Triple
T31077022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic II |
E791993
|
entity |
| Predicate | predecessorAsKingOfBurgundy |
P188891
|
FINISHED |
| Object | Childebert 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: Childebert II | Statement: [Theuderic II, predecessorAsKingOfBurgundy, Childebert II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsKingOfBurgundy Context triple: [Theuderic II, predecessorAsKingOfBurgundy, Childebert II]
-
A.
predecessorAsDukeOfLorraine
Indicates that one entity held the title of Duke of Lorraine immediately before another 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.
predecessorAsKingOfEastFrancia
Indicates that one person previously held the position of King of East Francia immediately before another person.
-
E.
successorAsDukeOfBurgundy
Indicates that one entity became the next Duke of Burgundy following another entity in the line of 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_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: April 29, 2026, 9:02 p.m.