Triple

T36398981
Position Surface form Disambiguated ID Type / Status
Subject Titcomb Basin E896566 entity
Predicate hasNotableNearbyPeak P7612 FINISHED
Object Bow Mountain
Bow Mountain is a prominent alpine peak in the Wind River Range of Wyoming, known for its rugged terrain and proximity to the glacial lakes and cliffs of Titcomb Basin.
E2289252 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: Bow Mountain | Statement: [Titcomb Basin, hasNotableNearbyPeak, Bow Mountain]
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: Bow Mountain
Triple: [Titcomb Basin, hasNotableNearbyPeak, Bow Mountain]
Generated description
Bow Mountain is a prominent alpine peak in the Wind River Range of Wyoming, known for its rugged terrain and proximity to the glacial lakes and cliffs of Titcomb Basin.

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_6a5b15601d34819091fb081d9c130e57 completed July 18, 2026, 5:55 a.m.
NEDg Description generation batch_6a5b161bce288190a8bbeb752584567a completed July 18, 2026, 5:58 a.m.
NED2 Entity disambiguation (via description) batch_6a5b16b861fc819082545c06369b9cfa completed July 18, 2026, 6:01 a.m.
Created at: May 3, 2026, 4:10 p.m.