Triple

T36399047
Position Surface form Disambiguated ID Type / Status
Subject Titcomb Basin E896566 entity
Predicate hasNotableNearbyPeak P7612 FINISHED
Object Pingora's Crack
Pingora's Crack is a renowned rock climbing route on Pingora Peak in Wyoming's Wind River Range, celebrated for its classic crack climbing on high-quality granite.
E2181981 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: Pingora's Crack | Statement: [Titcomb Basin, hasNotableNearbyPeak, Pingora's Crack]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Pingora's Crack
Triple: [Titcomb Basin, hasNotableNearbyPeak, Pingora's Crack]
Generated description
Pingora's Crack is a renowned rock climbing route on Pingora Peak in Wyoming's Wind River Range, celebrated for its classic crack climbing on high-quality granite.

Provenance (5 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_69f76e53b81081908d3b81860593f38a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a03809bd57c8190beb371feaf44a7db completed May 12, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39b44252fc8190b44fbf6573c1a0ac completed June 22, 2026, 10:16 p.m.
NEDg Description generation batch_6a39b51633788190bb28cd4f30b7d19c completed June 22, 2026, 10:20 p.m.
NED2 Entity disambiguation (via description) batch_6a39b7796e1c81909600a1b006e33ac8 completed June 22, 2026, 10:30 p.m.
Created at: May 3, 2026, 4:10 p.m.