Triple

T15572040
Position Surface form Disambiguated ID Type / Status
Subject Ryan Mountain E374268 entity
Predicate hasSummit P8024 FINISHED
Object Ryan Mountain summit 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: Ryan Mountain summit | Statement: [Ryan Mountain, hasSummit, Ryan Mountain summit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ryan Mountain summit
Context triple: [Ryan Mountain, hasSummit, Ryan Mountain summit]
  • A. Ryan Mountain chosen
    Ryan Mountain is a prominent peak in Joshua Tree National Park, California, known for its panoramic desert views and popularity among hikers.
  • B. Hyndman Peak
    Hyndman Peak is a prominent mountain summit in central Idaho known for its challenging climbs and scenic alpine views.
  • C. Cam Peak
    Cam Peak is a prominent hill in Gloucestershire, England, known for its distinctive conical shape and panoramic views over the surrounding countryside.
  • D. Boistfort Peak
    Boistfort Peak is the highest summit in southwestern Washington’s Willapa Hills, known for its forested slopes and regional prominence.
  • E. Roundtop Mountain
    Roundtop Mountain is a stratovolcano located on Unimak Island in Alaska’s Aleutian Islands chain.
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e2025888190a2b6240296bba13e completed April 16, 2026, 2:49 a.m.
Created at: April 10, 2026, 4:10 a.m.