Triple

T13297140
Position Surface form Disambiguated ID Type / Status
Subject Mount Bierstadt E316713 entity
Predicate hasRidgeConnectionTo P30691 FINISHED
Object Mount Evans via Sawtooth Ridge LITERAL 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: Mount Evans via Sawtooth Ridge | Statement: [Mount Bierstadt, hasRidgeConnectionTo, Mount Evans via Sawtooth Ridge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRidgeConnectionTo
Context triple: [Mount Bierstadt, hasRidgeConnectionTo, Mount Evans via Sawtooth Ridge]
  • A. associatedWithRidge
    Indicates that one entity has a spatial, structural, or contextual connection or relationship to a ridge.
  • B. isRidge
    Indicates that something has the form or function of a ridge, typically being a long, narrow raised or elevated feature relative to its surroundings.
  • C. ridgeConnection chosen
    Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
  • D. hasRidges
    Indicates that one entity possesses raised, linear or patterned ridges on its surface or structure in relation to another entity or context.
  • E. hasTrailConnection
    Indicates that one location is connected to another by a traversable trail or path.
  • F. None of above.

Provenance (3 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f6893708190aeebf4c47386cff7 completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:28 p.m.