Triple
T36556216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärnur |
E901704
|
entity |
| Predicate | governanceAfterReign |
P106462
|
FINISHED |
| Object | Ruling Stewards of Gondor |
E732663
|
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: Ruling Stewards of Gondor | Statement: [Eärnur, governanceAfterReign, Ruling Stewards of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceAfterReign Context triple: [Eärnur, governanceAfterReign, Ruling Stewards of Gondor]
-
A.
appliesAfterReignOf
chosen
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
-
B.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
-
C.
governedSuccessionOf
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
-
D.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
concludedDuringReignOf
Indicates that an event, process, or state came to an end while a particular ruler’s reign or period of authority was ongoing.
- F. None of above.
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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f69f294308190aec30937221601de |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: May 3, 2026, 4:11 p.m.