Triple
T17426811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 KY26 |
E423757
|
entity |
| Predicate | isVerySmallNEA |
P127415
|
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: [1998 KY26, isVerySmallNEA, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVerySmallNEA Context triple: [1998 KY26, isVerySmallNEA, true]
-
A.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
B.
hasSmallBodyPopulation
Indicates that an entity has a relatively low number of small celestial bodies (such as asteroids, comets, or minor planets) associated with it.
-
C.
isDwarfPlanetCandidate
Indicates that an object is considered a potential dwarf planet based on current observational data and classification criteria.
-
D.
isOneOfMostMassiveTransNeptunianObjects
Indicates that the subject is among the most massive known objects located beyond Neptune in the Solar System.
-
E.
isSatelliteDwarfOf
Indicates that one celestial body is a smaller, gravitationally bound companion orbiting another, larger primary body.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fcbf54819091babed0b9b05716 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.