Triple
T36611735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewards of Gondor |
E903481
|
entity |
| Predicate | beganRulingAfter |
P4400
|
FINISHED |
| Object | loss of the kings of Gondor |
—
|
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: loss of the kings of Gondor | Statement: [Stewards of Gondor, beganRulingAfter, loss of the kings of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRulingAfter Context triple: [Stewards of Gondor, beganRulingAfter, loss of the kings of Gondor]
-
A.
governingSince
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
B.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
C.
inauguratedReignOf
Indicates that one entity formally began or initiated the period of rule or reign of another entity.
-
D.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
E.
cameToPowerAfter
chosen
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.