Triple
T32362808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Alemannia |
E826909
|
entity |
| Predicate | historicalSuccessorOffice |
P198853
|
FINISHED |
| Object | Duke of Swabia |
—
|
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: Duke of Swabia | Statement: [King of Alemannia, historicalSuccessorOffice, Duke of Swabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuccessorOffice Context triple: [King of Alemannia, historicalSuccessorOffice, Duke of Swabia]
-
A.
successorOfficeTo
Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
-
B.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
C.
successorOfficeHolder
Indicates that one office holder directly follows another in occupying the same official position.
-
D.
declaresSuccessorOffice
Indicates that an entity formally designates another entity to assume a particular office or position as its successor.
-
E.
successorOfficeContext
chosen
Indicates that one office or position directly follows and replaces another within a specific organizational or institutional context.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 1, 2026, 12:50 a.m.