Triple
T38130287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis II |
E952199
|
entity |
| Predicate | successorInBurgundy |
P198188
|
FINISHED |
| Object | Chlothar III |
—
|
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 III | Statement: [Clovis II, successorInBurgundy, Chlothar III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInBurgundy Context triple: [Clovis II, successorInBurgundy, Chlothar III]
-
A.
successorAsKingOfBurgundy
chosen
Indicates that one person became the next king of Burgundy following another person’s reign.
-
B.
successorAsDukeOfBurgundy
Indicates that one entity became the next Duke of Burgundy following another entity in the line of succession.
-
C.
predecessorInBurgundy
Indicates that one entity previously held a position, role, or status in Burgundy that was later held by the other entity.
-
D.
successorAsDukeOfBrittany
Indicates that one entity became the next Duke of Brittany following another entity in the line of succession.
-
E.
successorAsDukeOfAnjou
Indicates that one entity became the next holder of the title Duke of Anjou after another entity.
- F. None of above.
Provenance (3 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_6a00d508290081909f3d5dfbb2e80c8e |
completed | May 10, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_6a00d49da4cc81909566ad286ec22292 |
completed | May 10, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:21 p.m.