Triple
T19260006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1604 Tombaugh |
E481621
|
entity |
| Predicate | orbitalFamily |
P111182
|
FINISHED |
| Object | main belt |
—
|
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: main belt | Statement: [1604 Tombaugh, orbitalFamily, main belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalFamily Context triple: [1604 Tombaugh, orbitalFamily, main belt]
-
A.
hasOrbitalFamily
chosen
Indicates that one celestial body belongs to the same group or class of objects that share similar orbital characteristics with another.
-
B.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
C.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
D.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
E.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8858588190a04e2a01e43fb7b2 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.