Triple

T11047016
Position Surface form Disambiguated ID Type / Status
Subject Gondor E261160 entity
Predicate foundedBy P104 FINISHED
Object Isildur E708663 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: Isildur | Statement: [Gondor, foundedBy, Isildur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isildur
Context triple: [Gondor, foundedBy, Isildur]
  • A. Isildur chosen
    Isildur is a legendary Númenórean prince and later King of Gondor and Arnor in J.R.R. Tolkien’s legendarium, best known for cutting the One Ring from Sauron’s hand and ultimately failing to destroy it.
  • B. Húrin Thalion
    Húrin Thalion is a legendary Man of the House of Hador in J.R.R. Tolkien’s Middle-earth, renowned for his valor in the First Age and his tragic defiance of Morgoth.
  • C. Elros
    Elros is a character from J.R.R. Tolkien’s legendarium, a Half-elven leader who chose mortality and became the first King of Númenor.
  • D. Anárion
    Anárion is a Númenórean prince from J.R.R. Tolkien’s legendarium, co-founder of Gondor alongside his brother Isildur and son of Elendil.
  • E. Elessar
    Elessar is the royal name of Aragorn, the Dúnedain ranger who becomes King of Gondor in J.R.R. Tolkien’s The Lord of the Rings.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa979bdc8190bf0e79104cc098c1 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d798307da481908996557a73c9b49a completed April 9, 2026, 12:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69e441a5b5a481908a6fdf5f8e9bca8b completed April 19, 2026, 2:44 a.m.
Created at: April 8, 2026, 9:26 p.m.