Triple
T35119244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Iron Throne |
E1014121
|
entity |
| Predicate | firstRulerToSit |
P206842
|
FINISHED |
| Object | Aegon I Targaryen |
E1090982
|
NE 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: Aegon I Targaryen | Statement: [the Iron Throne, firstRulerToSit, Aegon I Targaryen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRulerToSit Context triple: [the Iron Throne, firstRulerToSit, Aegon I Targaryen]
-
A.
firstMonarch
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
C.
firstMonarchOfCurrentDynastyReignStart
Indicates the date or time when the reign of the first monarch of the current ruling dynasty began.
-
D.
traditionalFirstEmperor
Indicates that the subject is regarded, in traditional or legendary accounts, as the first emperor of the object polity or realm.
-
E.
foundingEmperor
Indicates the person who established or first ruled an empire as its original sovereign.
- F. None of above. chosen
Provenance (5 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb0833308190a3d40c5b30fd1037 |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.