Triple

T25638279
Position Surface form Disambiguated ID Type / Status
Subject Valetudo E642764 entity
Predicate isInOrbitalResonance P17319 FINISHED
Object no known strong 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: no known strong resonance | Statement: [Valetudo, isInOrbitalResonance, no known strong resonance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInOrbitalResonance
Context triple: [Valetudo, isInOrbitalResonance, no known strong resonance]
  • A. hasOrbitalResonancePhenomena
    Indicates that there exists a dynamical relationship in which the orbital periods of two or more bodies are in a simple integer ratio, producing resonance effects such as repeated gravitational interactions or stable orbital configurations.
  • B. 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.
  • C. hasOrbitalResonanceHistory
    Indicates that there has been a past or present orbital resonance relationship between two celestial bodies or systems.
  • D. hasOrbitalPeriod
    Indicates that one entity completes a full orbit around another entity within a specified duration.
  • E. isOrbital
    Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central 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_69e77e7ce28081908b08d65ee6e5c8be completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fa64332081909df65f8b4380f152 completed May 2, 2026, 1:21 p.m.
PD Predicate disambiguation batch_69f4807f8680819098a524158d049c63 completed May 1, 2026, 10:29 a.m.
Created at: April 21, 2026, 5:37 p.m.