Triple

T29704910
Position Surface form Disambiguated ID Type / Status
Subject NOAA-14 E751598 entity
Predicate orbitCharacteristics P58578 FINISHED
Object near-circular Sun-synchronous polar 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: near-circular Sun-synchronous polar orbit | Statement: [NOAA-14, orbitCharacteristics, near-circular Sun-synchronous polar orbit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orbitCharacteristics
Context triple: [NOAA-14, orbitCharacteristics, near-circular Sun-synchronous polar orbit]
  • A. hasOrbitalCharacteristic chosen
    Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
  • B. orbitalEccentricity
    Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
  • C. orbitType
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • D. hasOrbitalPeriod
    Indicates that one entity completes a full orbit around another entity within a specified duration.
  • E. orbitShape
    Indicates the geometric form or path pattern that an orbiting object follows around another body.
  • 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_69f0d6266f8481909e70bb41cda18587 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f672b77cf4819099ab884963562c79 completed May 2, 2026, 9:55 p.m.
PD Predicate disambiguation batch_69f6659f246081909821c5f452d14e8f completed May 2, 2026, 8:59 p.m.
Created at: April 28, 2026, 7:26 p.m.