Triple

T25638946
Position Surface form Disambiguated ID Type / Status
Subject Sinope E642780 entity
Predicate tidalInteractionWithJupiter P119123 FINISHED
Object weak 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: weak | Statement: [Sinope, tidalInteractionWithJupiter, weak]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tidalInteractionWithJupiter
Context triple: [Sinope, tidalInteractionWithJupiter, weak]
  • A. tidalInteraction chosen
    Indicates that two astronomical bodies exert mutual tidal forces that exchange angular momentum and energy, altering their rotations and orbits over time.
  • B. isTidalInteractionSuspected
    Indicates that a gravitational interaction between astronomical bodies is suspected to be causing observable tidal effects or disturbances.
  • C. relationToJupiter
    Indicates a spatial or conceptual relationship that an entity has with the planet Jupiter, such as position, distance, or association relative to it.
  • D. hasTisserandParameterWithRespectToJupiter
    Indicates that an object has a specific value of the Tisserand parameter measured with respect to Jupiter, characterizing its dynamical relationship and orbital interaction with Jupiter.
  • E. isTidallyLockedWith
    Indicates that two astronomical bodies always show the same face to each other because one’s rotation period matches its orbital period around the other.
  • 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:38 p.m.