feat(phase-05/26): add quiz.json

This commit is contained in:
Rohit Ghumare
2026-05-23 01:04:58 +01:00
parent c9b2a7feca
commit 5e851175a3
@@ -0,0 +1,102 @@
{
"lesson": "26-relation-extraction-kg",
"title": "Relation Extraction & Knowledge Graph Construction",
"questions": [
{
"stage": "pre",
"question": "What is the atomic unit of a knowledge graph?",
"options": [
"A token",
"A (subject, relation, object) triple",
"A POS tag",
"A sentence"
],
"correct": 1,
"explanation": "KGs store information as (s, r, o) triples; aggregated triples form the graph."
},
{
"stage": "pre",
"question": "What does AEVS stand for in 2026 relation extraction?",
"options": [
"Async Entity Validation Service",
"Anchor-Extraction-Verification-Supplement: anchor spans, extract triples, verify against source, supplement coverage",
"Auto-Encoder Vector Search",
"Aggregated Entity-Value Schema"
],
"correct": 1,
"explanation": "AEVS is the 2026 hallucination-mitigation framework for grounded RE."
},
{
"stage": "check",
"question": "Why must each triple carry source provenance (doc id + span)?",
"options": [
"It speeds up extraction",
"Provenance lets you audit triples and reject hallucinations whose spans do not match the source text",
"Provenance is required by SPARQL",
"Provenance changes the ontology"
],
"correct": 1,
"explanation": "Provenance enables auditing and is the core of AEVS-style hallucination detection."
},
{
"stage": "check",
"question": "What does canonicalization of relations do?",
"options": [
"Removes triples",
"Maps surface verb phrases (e.g. 'was born in', 'is a native of') onto a fixed property id so the graph is queryable",
"Translates the document",
"Adds embeddings"
],
"correct": 1,
"explanation": "Canonicalization collapses paraphrases into canonical KG property ids."
},
{
"stage": "check",
"question": "Why does relation extraction usually need coreference resolution first?",
"options": [
"Coref normalizes case",
"Pronouns like 'he founded Apple' must be resolved to a named entity before triple extraction",
"Coref adds embeddings",
"Coref provides positions"
],
"correct": 1,
"explanation": "Without coref, RE attaches relations to pronouns instead of the underlying named entity."
},
{
"stage": "post",
"question": "Which choice trades open IE recall for graph queryability?",
"options": [
"Embedding-only graphs",
"Mapping open-IE relations onto a closed ontology (e.g. Wikidata properties) before merging into the KG",
"Random sampling of triples",
"Skipping NER"
],
"correct": 1,
"explanation": "Closed ontologies make the graph queryable; the canonicalization step pays for itself downstream."
},
{
"stage": "post",
"question": "Why do many production KGs use temporal qualifiers (start/end time)?",
"options": [
"Faster SPARQL",
"Many relations are time-bounded (employer, spouse, role); qualifiers prevent 'forever true' claims that go stale",
"Required by RDF",
"To remove NIL entities"
],
"correct": 1,
"explanation": "Time-bounded relations need qualifiers (e.g. Wikidata P580/P582) or facts go silently stale."
},
{
"stage": "post",
"question": "What is REBEL?",
"options": [
"A vector database",
"A seq2seq relation extractor that outputs triples already in Wikidata property ids",
"A coreference model",
"A tokenizer"
],
"correct": 1,
"explanation": "REBEL (Babelscape) is a seq2seq RE model trained on distantly supervised Wikidata triples."
}
]
}