Triple

T5036845
Position Surface form Disambiguated ID Type / Status
Subject Moffat Tunnel route E113445 entity
Predicate hasMaximumElevationApprox P46534 FINISHED
Object over 9,000 feet above sea level 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: over 9,000 feet above sea level | Statement: [Moffat Tunnel route, hasMaximumElevationApprox, over 9,000 feet above sea level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMaximumElevationApprox
Context triple: [Moffat Tunnel route, hasMaximumElevationApprox, over 9,000 feet above sea level]
  • A. hasTopElevation chosen
    Indicates that an entity has a specified maximum or highest elevation value.
  • B. hasApproxElevationFeet
    Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
  • C. hasElevationFeature
    Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
  • D. elevationApproxMeters
    Indicates the approximate elevation of an entity above sea level, measured in meters.
  • E. hasAverageElevation
    Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
  • 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_69bd44384298819089c49e7c330ec7b8 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73bb069c8190af86f1b2f95f3d95 completed March 20, 2026, 4:20 p.m.
PD Predicate disambiguation batch_69bd71529d608190a53470ba6c14bb1d completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:37 p.m.