Triple
T30633327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gil-galad |
E779766
|
entity |
| Predicate | successorAsHighKing |
P197559
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Gil-galad, successorAsHighKing, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsHighKing Context triple: [Gil-galad, successorAsHighKing, none]
-
A.
successorAsKingOfKings
Indicates that one entity directly follows another in holding the title or role of King of Kings.
-
B.
successorAsTitularKing
Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
-
C.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
D.
successorAsPrince
Indicates that one individual directly follows another in holding the title or role of prince.
-
E.
successorAsLordOf
Indicates that one entity takes over the role or title of lord from another entity, becoming their direct successor in that lordship.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: April 29, 2026, 8:28 p.m.