Triple
T37330140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maedhros |
E926720
|
entity |
| Predicate | cededKingshipTo |
P7967
|
FINISHED |
| Object | Fingon |
—
|
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: Fingon | Statement: [Maedhros, cededKingshipTo, Fingon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cededKingshipTo Context triple: [Maedhros, cededKingshipTo, Fingon]
-
A.
succeededOnThroneAfter
Indicates that one entity became the ruler or monarch immediately following another entity’s reign on the same throne.
-
B.
succeededToThroneBy
Indicates that one ruler or monarch is followed in succession by another who takes over the throne.
-
C.
resultedInSuccessionTo
Indicates that one event, action, or circumstance caused or led directly to a change in who holds a position, title, or role, resulting in a new successor taking over.
-
D.
abdicatedInFavorOf
chosen
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
-
E.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.