Triple

T19133069
Position Surface form Disambiguated ID Type / Status
Subject (416400) 2003 UZ117 E468362 entity
Predicate orbitalClassification P7214 FINISHED
Object classical Kuiper Belt object 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: classical Kuiper Belt object | Statement: [(416400) 2003 UZ117, orbitalClassification, classical Kuiper Belt object]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orbitalClassification
Context triple: [(416400) 2003 UZ117, orbitalClassification, classical Kuiper Belt object]
  • A. orbitType chosen
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • B. isOrbital
    Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
  • C. hasOrbitalCharacteristic
    Indicates that an entity possesses a specific property or feature related to its orbit, such as shape, period, inclination, or other orbital parameters.
  • D. orbitalBodyType
    Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
  • E. orbitalAssociation
    Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another 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_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.
Created at: April 10, 2026, 12:05 p.m.