Triple
T4531593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dysnomia |
E106309
|
entity |
| Predicate | hasOrbitalResonance |
P17319
|
FINISHED |
| Object | none known with other bodies |
—
|
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: none known with other bodies | Statement: [Dysnomia, hasOrbitalResonance, none known with other bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalResonance Context triple: [Dysnomia, hasOrbitalResonance, none known with other bodies]
-
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.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
-
D.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.