Triple
T5725902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europa |
E126262
|
entity |
| Predicate | resonantOrbitalRelationship |
P17319
|
FINISHED |
| Object | in 2:1 resonance with Io |
—
|
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: in 2:1 resonance with Io | Statement: [Europa, resonantOrbitalRelationship, in 2:1 resonance with Io]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resonantOrbitalRelationship Context triple: [Europa, resonantOrbitalRelationship, in 2:1 resonance with Io]
-
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.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
C.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
D.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
-
E.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.