Triple
T7441066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganymede |
E171752
|
entity |
| Predicate | orbitalResonanceRatioWithIo |
P17319
|
FINISHED |
| Object | 1:4 |
—
|
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: 1:4 | Statement: [Ganymede, orbitalResonanceRatioWithIo, 1:4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalResonanceRatioWithIo Context triple: [Ganymede, orbitalResonanceRatioWithIo, 1:4]
-
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.
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.
-
C.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
-
D.
massInJupiterOrbit
Indicates the mass an object has while it is located in orbit around Jupiter.
-
E.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f34d84008190936af2b3670ef210 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:13 p.m.