Triple

T11000545
Position Surface form Disambiguated ID Type / Status
Subject Sun-synchronous orbit E259991 entity
Predicate hasNodalPrecessionRate P27812 FINISHED
Object approximately 360 degrees per year 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 360 degrees per year | Statement: [Sun-synchronous orbit, hasNodalPrecessionRate, approximately 360 degrees per year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNodalPrecessionRate
Context triple: [Sun-synchronous orbit, hasNodalPrecessionRate, approximately 360 degrees per year]
  • A. nodePrecessionPeriod chosen
    Indicates the duration of time it takes for the line of nodes of an orbit to complete one full precessional cycle relative to a reference frame.
  • B. hasRotationalVelocityKmPerSec
    Indicates that an entity possesses a rotational speed measured in kilometers per second.
  • C. hasObliquityPeriod
    Indicates the relationship between an object and the duration of its axial tilt (obliquity) cycle.
  • D. hasOrbitalPeriod
    Indicates that one entity completes a full orbit around another entity within a specified duration.
  • E. hasRotationalVelocity
    Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
  • 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_69d6aa8a6a548190a750f944ccdc8064 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d796d68b608190a8d016b9383e82f8 completed April 9, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69d72e93ac648190b46c5d12bf3eb1e9 completed April 9, 2026, 4:44 a.m.
Created at: April 8, 2026, 9:25 p.m.