Triple

T989657
Position Surface form Disambiguated ID Type / Status
Subject Missouri River E21358 entity
Predicate mouthElevation P221 FINISHED
Object approximately 122 meters 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: approximately 122 meters | Statement: [Missouri River, mouthElevation, approximately 122 meters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mouthElevation
Context triple: [Missouri River, mouthElevation, approximately 122 meters]
  • A. elevation chosen
    Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
  • B. mouthOf
    Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
  • C. mouthNear
    Indicates that one entity’s mouth is positioned close to another entity or object in space.
  • D. mouth
    Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
  • E. elevationAtBase
    Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference 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_69a493c383dc8190a03257f22d4b4183 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4aa16f081909dcc7a7ce3fb1b64 completed March 1, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69a4b2adbde48190b07966d0c3179516 completed March 1, 2026, 9:42 p.m.
Created at: March 1, 2026, 7:41 p.m.