Triple

T2994700
Position Surface form Disambiguated ID Type / Status
Subject low Earth orbit E81038 entity
Predicate hasTypicalAltitudeUpperBound P6750 FINISHED
Object about 2,000 kilometers above Earth’s surface 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: about 2,000 kilometers above Earth’s surface | Statement: [low Earth orbit, hasTypicalAltitudeUpperBound, about 2,000 kilometers above Earth’s surface]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalAltitudeUpperBound
Context triple: [low Earth orbit, hasTypicalAltitudeUpperBound, about 2,000 kilometers above Earth’s surface]
  • A. locatedAtAltitude
    Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
  • B. altitudeCapability chosen
    Indicates the maximum or typical altitude at which an entity can effectively operate or function.
  • C. hasAltitudeStation
    Indicates that something is associated with or located at a station characterized by a specific altitude.
  • D. altitudeOfRecordFlight
    Indicates the altitude reached during a particular record-setting flight.
  • E. heightRestriction
    Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
  • 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_69ad8b187fc8819085914d3c9ea3142d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99f2e5888190b3346012e2578dab completed March 8, 2026, 3:46 p.m.
PD Predicate disambiguation batch_69ad961403108190bbecb8d3608fd4e0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:59 p.m.