Triple
T18458212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28978 Ixion |
E450959
|
entity |
| Predicate | orbitalResonanceType |
P17319
|
FINISHED |
| Object | 2:3 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:3 resonance | Statement: [28978 Ixion, orbitalResonanceType, 2:3 resonance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalResonanceType Context triple: [28978 Ixion, orbitalResonanceType, 2:3 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.
hasOrbitalResonanceHistory
Indicates that there has been a past or present orbital resonance relationship between two celestial bodies or systems.
-
C.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
D.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.