Triple

T16203349
Position Surface form Disambiguated ID Type / Status
Subject Dagobert I E393259 entity
Predicate givenName P17 FINISHED
Object Dagobert E393259 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Dagobert | Statement: [Dagobert I, givenName, Dagobert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dagobert
Context triple: [Dagobert I, givenName, Dagobert]
  • A. Dagobert I chosen
    Dagobert I was a 7th-century Merovingian king who ruled over much of the Frankish realm and is often regarded as one of the last powerful monarchs of his dynasty.
  • B. Hrodebert
    Hrodebert is an ancient Germanic given name meaning "fame-bright" or "bright glory," from which later names like Robert and Roberto are derived.
  • C. Theuderic I
    Theuderic I was a 6th-century Merovingian king of the Franks, ruling from Reims and noted for his military campaigns and role in early Frankish expansion.
  • D. Heribert
    Heribert is the given name of Herbert von Karajan, the renowned 20th-century Austrian conductor.
  • E. Pepin
    Pepin was a Carolingian prince who ruled as King of Aquitaine in the early 9th century.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2270ca18c8190a259992aed4ec072 completed April 17, 2026, 12:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffff130bcc8190a965d90e123d2dd9 completed May 10, 2026, 3:44 a.m.
Created at: April 10, 2026, 5:03 a.m.