Triple

T11049086
Position Surface form Disambiguated ID Type / Status
Subject Undying Lands E261199 entity
Predicate contains P35 FINISHED
Object Tirion E819718 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: Tirion | Statement: [Undying Lands, contains, Tirion]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tirion
Context triple: [Undying Lands, contains, Tirion]
  • A. Tirion chosen
    Tirion is the chief Elven city in Aman in J.R.R. Tolkien’s legendarium, renowned as the white hill-city of the Noldor and Vanyar.
  • B. Courrendlin
    Courrendlin is a municipality in the French-speaking canton of Jura in northwestern Switzerland.
  • C. Rocherath
    Rocherath is a village in eastern Belgium, close to the German border, known for its location near key World War II Battle of the Bulge sites.
  • D. Landore
    Landore is a district of Swansea in South Wales, known historically for its industrial heritage and proximity to the River Tawe.
  • E. Eryn Galen
    Eryn Galen is the original Elvish name for the great forest later known as Mirkwood in J.R.R. Tolkien’s Middle-earth legendarium.
  • 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_69d6aa98650481908609c7c56bfa7902 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79867fa28819094f564273e3ef51d completed April 9, 2026, 12:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3c851d5408190b12250a2a1322874 completed April 18, 2026, 6:07 p.m.
Created at: April 8, 2026, 9:26 p.m.