Triple
T31077023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic II |
E791993
|
entity |
| Predicate | successorAsKingOfBurgundy |
P198188
|
FINISHED |
| Object | Chlothar II |
—
|
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: Chlothar II | Statement: [Theuderic II, successorAsKingOfBurgundy, Chlothar II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKingOfBurgundy Context triple: [Theuderic II, successorAsKingOfBurgundy, Chlothar II]
-
A.
successorAsDukeOfBurgundy
Indicates that one entity became the next Duke of Burgundy following another entity in the line of succession.
-
B.
predecessorAsKingOfBurgundy
Indicates that one entity served as the immediately preceding king of Burgundy to the other entity.
-
C.
successorAsDukeOfAnjou
Indicates that one entity became the next holder of the title Duke of Anjou after another entity.
-
D.
successorAsDukeOfBrittany
Indicates that one entity became the next Duke of Brittany following another entity in the line of succession.
-
E.
successorAsKingOfFrance
Indicates that one person becomes the next king of France following another person in the royal succession.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: April 29, 2026, 9:02 p.m.