Triple
T2776131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand II, Holy Roman Emperor |
E61573
|
entity |
| Predicate | reignAsKingOfHungaryEnd |
P43111
|
FINISHED |
| Object | 1637 |
—
|
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: 1637 | Statement: [Ferdinand II, Holy Roman Emperor, reignAsKingOfHungaryEnd, 1637]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsKingOfHungaryEnd Context triple: [Ferdinand II, Holy Roman Emperor, reignAsKingOfHungaryEnd, 1637]
-
A.
reignAsKingOfHungaryStart
Indicates the time at which an individual begins their reign as king of Hungary.
-
B.
reignAsKingOfPolandEnd
Indicates the time or event at which an individual’s reign as King of Poland comes to an end.
-
C.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
D.
reignEndAsEmperorOfAustria
Indicates the date or event marking when an individual’s tenure as Emperor of Austria came to an end.
-
E.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:57 p.m.