Triple
T28890081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Tower of Ecthelion |
E732670
|
entity |
| Predicate | laterRulerResident |
P129984
|
FINISHED |
| Object | King Elessar |
—
|
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: King Elessar | Statement: [White Tower of Ecthelion, laterRulerResident, King Elessar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRulerResident Context triple: [White Tower of Ecthelion, laterRulerResident, King Elessar]
-
A.
laterRulerTitle
Indicates that an entity held a particular ruler title at a later point in time, after some earlier status or title.
-
B.
ruledLaterBy
chosen
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
C.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
D.
governedAsRegentFrom
Indicates that an individual exercised governing authority as a regent over a territory or polity, starting from a specified point in time.
-
E.
laterHeir
Indicates that one entity becomes the heir of another at a later time, succeeding a prior heir or following a change in succession.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 28, 2026, 7:54 a.m.