Triple

T18478130
Position Surface form Disambiguated ID Type / Status
Subject Pantheon Range E451485 entity
Predicate hasPeak P8205 FINISHED
Object Mount Tiedemann 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: Mount Tiedemann | Statement: [Pantheon Range, hasPeak, Mount Tiedemann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Tiedemann
Context triple: [Pantheon Range, hasPeak, Mount Tiedemann]
  • A. Mount Tiedemann chosen
    Mount Tiedemann is a prominent glaciated peak in British Columbia’s Coast Mountains, known for its rugged alpine terrain and challenging mountaineering routes.
  • B. Mount Waesche
    Mount Waesche is a large, mostly ice-covered shield volcano located at the southern end of the Executive Committee Range in Marie Byrd Land, Antarctica.
  • C. Mount Reimer
    Mount Reimer is a mountain peak in the Sentinel Range of the Ellsworth Mountains in Western Antarctica.
  • D. Mount Tottan
    Mount Tottan is a mountain peak located within the Sør Rondane Mountains of Queen Maud Land in Antarctica.
  • E. Mount Degenhardt
    Mount Degenhardt is a rugged granite peak in Washington State’s North Cascades, known for its challenging alpine climbing routes within the remote Picket Range.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38465a0819099b9b42d2a662ac1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53064a7548190b712a14ad0c7a477 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 11:35 a.m.