Triple

T15480106
Position Surface form Disambiguated ID Type / Status
Subject Sunshine Peak E376891 entity
Predicate near P350 FINISHED
Object Handies Peak 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: Handies Peak | Statement: [Sunshine Peak, near, Handies Peak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Handies Peak
Context triple: [Sunshine Peak, near, Handies Peak]
  • A. Handies Peak chosen
    Handies Peak is a prominent fourteener in southwestern Colorado, known for its scenic alpine views within the San Juan Mountains.
  • B. Pamola Peak
    Pamola Peak is a prominent sub-peak on Maine’s Mount Katahdin, known as the eastern terminus of the exposed Knife Edge ridge and for its dramatic, rugged cliffs.
  • C. Hyndman Peak
    Hyndman Peak is a prominent mountain summit in central Idaho known for its challenging climbs and scenic alpine views.
  • D. Ruen Peak
    Ruen Peak is the highest summit of the Osogovo mountain range, located on the border between Bulgaria and North Macedonia.
  • E. Wright Peak
    Wright Peak is a prominent High Peak in New York’s Adirondack Mountains, popular with hikers for its open summit and expansive views.
  • 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f8a77a081909f12f13660452f4a completed April 16, 2026, 1:46 a.m.
Created at: April 10, 2026, 3:34 a.m.