Triple
T31077025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic II |
E791993
|
entity |
| Predicate | successorAsKingOfAustrasia |
P198215
|
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, successorAsKingOfAustrasia, Chlothar II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKingOfAustrasia Context triple: [Theuderic II, successorAsKingOfAustrasia, Chlothar II]
-
A.
successorAsKingOfTheFranks
Indicates that one person became the next king of the Franks after another person.
-
B.
successorAsKingOfWestFrancia
Indicates that one person became the next king of West Francia after another person, directly following them in that royal succession.
-
C.
predecessorAsKingOfAustrasia
Indicates that one entity previously held the position of king of Austrasia immediately before another entity.
-
D.
successorAsCarolingianRuler
Indicates that one entity became the next Carolingian ruler directly following another in the line of succession.
-
E.
predecessorAsKingOfEastFrancia
Indicates that one person previously held the position of King of East Francia immediately before another person.
- 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_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69fed3569ca881909f4291baeb665d9d |
completed | May 9, 2026, 6:25 a.m. |
Created at: April 29, 2026, 9:02 p.m.