Triple
T18458285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 55636 2002 TX300 |
E450960
|
entity |
| Predicate | isNearDwarfPlanetSizeThreshold |
P51232
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [55636 2002 TX300, isNearDwarfPlanetSizeThreshold, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearDwarfPlanetSizeThreshold Context triple: [55636 2002 TX300, isNearDwarfPlanetSizeThreshold, true]
-
A.
isDwarfPlanetCandidate
chosen
Indicates that an object is considered a potential dwarf planet based on current observational data and classification criteria.
-
B.
hasDwarfPlanet
Indicates that one entity possesses or is associated with a dwarf planet as part of its system or domain.
-
C.
isVerySmallNEA
Indicates that an object is classified as a very small near-Earth asteroid relative to typical NEAs.
-
D.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
E.
isOneOfMostMassiveTransNeptunianObjects
Indicates that the subject is among the most massive known objects located beyond Neptune in the Solar System.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.