Triple
T31077024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic II |
E791993
|
entity |
| Predicate | predecessorAsKingOfAustrasia |
P189346
|
FINISHED |
| Object | Theudebert 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: Theudebert II | Statement: [Theuderic II, predecessorAsKingOfAustrasia, Theudebert II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsKingOfAustrasia Context triple: [Theuderic II, predecessorAsKingOfAustrasia, Theudebert II]
-
A.
predecessorAsKingOfWestFrancia
Indicates that one entity served as the immediately preceding king of West Francia relative to another entity.
-
B.
predecessorAsKingOfEastFrancia
Indicates that one person previously held the position of King of East Francia immediately before another person.
-
C.
predecessorAsDukeOfTheFranks
Indicates that one individual previously held the title of Duke of the Franks before another, establishing a direct succession relationship between them.
-
D.
successorAsKingOfTheFranks
Indicates that one person became the next king of the Franks after another person.
-
E.
successorInLotharingia
Indicates that one entity is the direct successor of another in ruling or holding authority over Lotharingia.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 29, 2026, 9:02 p.m.