Triple
T31920583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich der Vogler |
E814956
|
entity |
| Predicate | reignStartAsDukeOfSaxony |
P111737
|
FINISHED |
| Object | 0912 |
—
|
LITERAL FINISHED |
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: 0912 | Statement: [Heinrich der Vogler, reignStartAsDukeOfSaxony, 0912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsDukeOfSaxony Context triple: [Heinrich der Vogler, reignStartAsDukeOfSaxony, 0912]
-
A.
reignAsDukeOfSaxonyStart
chosen
Indicates the time at which an individual begins their tenure ruling in the position of Duke of Saxony.
-
B.
reignStartAsElectorOfSaxony
Indicates the date or point in time when an individual began their rule in the capacity of Elector of Saxony.
-
C.
reignAsDukeOfSaxonyEnd
Indicates the point in time or event at which an individual's tenure or rule as Duke of Saxony comes to an end.
-
D.
reignStartAsDukeOfAustria
Indicates the date or event marking when an individual began their reign holding the title of Duke of Austria.
-
E.
reignStartAsDukeOfCleves
Indicates the date or point in time when an individual began their reign holding the title of Duke of Cleves.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 12:03 a.m.