Triple

T2977053
Position Surface form Disambiguated ID Type / Status
Subject Transiting Exoplanet Survey Satellite E80422 entity
Predicate orbitResonance P17319 FINISHED
Object 2:1 lunar resonance 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: 2:1 lunar resonance | Statement: [Transiting Exoplanet Survey Satellite, orbitResonance, 2:1 lunar resonance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orbitResonance
Context triple: [Transiting Exoplanet Survey Satellite, orbitResonance, 2:1 lunar resonance]
  • A. hasOrbitalResonanceWith chosen
    Indicates that two orbiting bodies have orbital periods in a simple integer ratio, causing their gravitational influences to repeat in a regular, synchronized pattern.
  • B. orbits
    Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
  • C. coOrbitsWith
    Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
  • D. orbitType
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • E. orbitedBody
    Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
  • 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_69ad8b15f6ac8190be5fd16a33edcb4f completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad998c589c8190b4530f3fb8975187 completed March 8, 2026, 3:45 p.m.
PD Predicate disambiguation batch_69ad96105a708190a9ec4838cbcb1207 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.