Triple
T38130295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis II |
E952199
|
entity |
| Predicate | predecessorInBurgundy |
P197313
|
FINISHED |
| Object | Dagobert I |
—
|
NE NERFINISHED |
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 I | Statement: [Clovis II, predecessorInBurgundy, Dagobert I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInBurgundy Context triple: [Clovis II, predecessorInBurgundy, Dagobert I]
-
A.
predecessorAsKingOfBurgundy
Indicates that one entity served as the immediately preceding king of Burgundy to the other entity.
-
B.
predecessorAsDukeOfBrittany
Indicates that one entity previously held the title of Duke of Brittany immediately before another entity.
-
C.
predecessorAsDukeOfAnjou
Indicates that one entity previously held the title of Duke of Anjou before another entity, serving as that entity’s immediate predecessor in this ducal role.
-
D.
predecessorAsDukeOfOrléans
Indicates that one entity previously held the title of Duke of Orléans immediately before another entity, serving as that successor’s direct predecessor in the dukedom.
-
E.
predecessorAsDauphin
Indicates that one entity previously held the title or role of Dauphin immediately before another entity.
- F. None of above. chosen
Provenance (4 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: May 3, 2026, 4:21 p.m.