Triple
T3729475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20000 Varuna |
E79025
|
entity |
| Predicate | meanMotionResonance |
P27378
|
FINISHED |
| Object | none with Neptune |
—
|
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 with Neptune | Statement: [20000 Varuna, meanMotionResonance, none with Neptune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanMotionResonance Context triple: [20000 Varuna, meanMotionResonance, none with Neptune]
-
A.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
B.
resonanceWith
chosen
Indicates a relationship where one entity aligns, harmonizes, or meaningfully connects with another in a way that amplifies or reinforces its effect or significance.
-
C.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
D.
properMotion
Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
-
E.
properMotionDec
Indicates the rate of change of an object's position over time in the declination (north–south) direction on the celestial sphere.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.