Triple

T26681884
Position Surface form Disambiguated ID Type / Status
Subject United States Space Surveillance Network E672633 entity
Predicate tracksOrbitRegime P48448 FINISHED
Object highly elliptical orbit 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: highly elliptical orbit | Statement: [United States Space Surveillance Network, tracksOrbitRegime, highly elliptical orbit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tracksOrbitRegime
Context triple: [United States Space Surveillance Network, tracksOrbitRegime, highly elliptical orbit]
  • A. orbitType
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • B. supportsOrbitRegimes chosen
    Indicates that one entity is capable of operating in, accommodating, or being compatible with specific orbital regimes of another entity.
  • C. designedForOrbitType
    Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
  • D. orbitsEarth
    Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
  • E. coOrbitsWith
    Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
  • 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_69eecda13424819092b17942c4edf722 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6247480cc8190a887eedaeb94615c completed May 2, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69f623a7539c8190b71797f583da9f63 completed May 2, 2026, 4:17 p.m.
Created at: April 27, 2026, 3:20 a.m.