Triple

T4120820
Position Surface form Disambiguated ID Type / Status
Subject South Mount Elbert Trail E92606 entity
Predicate locatedOn P40 FINISHED
Object Mount Elbert E14075 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: Mount Elbert | Statement: [South Mount Elbert Trail, locatedOn, Mount Elbert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Elbert
Context triple: [South Mount Elbert Trail, locatedOn, Mount Elbert]
  • A. Mount Elbert chosen
    Mount Elbert is the highest peak in the Rocky Mountains and the tallest mountain in Colorado, located in the Sawatch Range.
  • B. Uncompahgre Peak
    Uncompahgre Peak is a prominent fourteener in southwestern Colorado, known for its broad summit and status as the highest point in the San Juan Mountains.
  • C. Elbert
    Elbert is a masculine given name of English origin, historically borne by figures such as American lawyer and steel industry executive Elbert H. Gary.
  • D. Longs Peak
    Longs Peak is a prominent fourteener in Colorado’s Front Range, renowned for its dramatic profile and challenging Keyhole Route climb.
  • E. Mount Sneffels
    Mount Sneffels is a prominent and rugged fourteener in southwestern Colorado, renowned for its dramatic profile and popular alpine climbing routes.
  • 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_69aed9685f70819086932777aec8d959 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69af0203b8c88190b08dd64800a37168 completed March 9, 2026, 5:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f22e2bc8190a99df0863cf6b2bf completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:41 p.m.