Triple
T30812978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elendil |
E784694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | High King of Arnor and Gondor |
C58309
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: High King of Arnor and Gondor Context triple: [Elendil, instanceOf, High King of Arnor and Gondor]
-
A.
Captain of Gondor
A Captain of Gondor is a high-ranking military leader responsible for commanding Gondorian forces in battle, upholding the realm’s defense, and exemplifying courage and loyalty to the Steward and people of Gondor.
-
B.
Dúnedain chieftain
A Dúnedain chieftain is the noble leader of the northern Rangers, descended from Númenórean kings and charged with protecting the lands of Eriador in secret.
-
C.
Steward of Gondor
The Steward of Gondor is the appointed ruler who governs the kingdom of Gondor in trust and in place of the absent king, managing its defense, laws, and affairs until the rightful monarch returns.
-
D.
ruler of Esgaroth
The ruler of Esgaroth is the political and administrative leader of the Lake-town community, responsible for governing its people, managing trade and resources, and representing the city in dealings with external powers.
-
E.
prince of Númenor
A prince of Númenor is a high-born male member of Númenórean royalty, typically in the line of succession, who embodies the island-kingdom’s noble lineage, maritime power, and often its internal conflicts between loyalty to the Valar and the lure of pride and dominion.
- F. None of above. chosen
Provenance (1 batch)
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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:43 p.m.