Triple
T3729507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (15760) 1992 QB1 |
E79026
|
entity |
| Predicate | distanceFromNeptune |
P51294
|
FINISHED |
| Object | not in strong mean-motion 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: not in strong mean-motion resonance | Statement: [(15760) 1992 QB1, distanceFromNeptune, not in strong mean-motion resonance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromNeptune Context triple: [(15760) 1992 QB1, distanceFromNeptune, not in strong mean-motion resonance]
-
A.
distanceToBigDiomede
Indicates the measured distance between a given entity’s location and Big Diomede Island.
-
B.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
C.
closestApproachToPlutoDistance
Indicates the minimum distance an object comes to Pluto at the point of its closest approach.
-
D.
hasMeanDistanceFromJupiter
Indicates that one entity has a specified average distance from the planet Jupiter.
-
E.
distanceFromEarthCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Earth.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.