Triple

T20810208
Position Surface form Disambiguated ID Type / Status
Subject Crestone Peaks E512276 entity
Predicate contains P35 FINISHED
Object Broken Hand Peak
Broken Hand Peak is a rugged sub-summit in Colorado’s Sangre de Cristo Range, closely associated with the Crestone group of fourteeners and popular with experienced climbers.
E1620723 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: Broken Hand Peak | Statement: [Crestone Peaks, contains, Broken Hand Peak]
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: Broken Hand Peak
Triple: [Crestone Peaks, contains, Broken Hand Peak]
Generated description
Broken Hand Peak is a rugged sub-summit in Colorado’s Sangre de Cristo Range, closely associated with the Crestone group of fourteeners and popular with experienced climbers.

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_69e0b4cd25088190b48ca9700cd24efc completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2d27a4881908b34679385d8b94b completed April 21, 2026, 12:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0facddecc08190b8054df90457baf3 completed May 22, 2026, 1:09 a.m.
NEDg Description generation batch_6a0fae10893c819092a3ecd95b6b9198 completed May 22, 2026, 1:14 a.m.
NED2 Entity disambiguation (via description) batch_6a0faf345eac8190b8a648c3add470bd completed May 22, 2026, 1:19 a.m.
Created at: April 16, 2026, 12:40 p.m.