Triple
T19132955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (55636) 2002 TX300 |
E468358
|
entity |
| Predicate | hasOrbitalUncertainty |
P134533
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [(55636) 2002 TX300, hasOrbitalUncertainty, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalUncertainty Context triple: [(55636) 2002 TX300, hasOrbitalUncertainty, low]
-
A.
hasOrbitalCharacteristic
Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
-
B.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
-
C.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
D.
hasOrbitalDecay
Indicates that one object’s orbit around another is gradually shrinking or degrading over time, typically due to forces like drag or gravitational interactions.
-
E.
hasOrbitalCause
Indicates that one entity’s state, behavior, or occurrence is caused by the orbital motion or orbital characteristics of another entity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ea82f08190811ef35fbae744d1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.