Triple
T992611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceres |
E21423
|
entity |
| Predicate | dwarfPlanetDesignationDate |
P22850
|
FINISHED |
| Object | 2006-08-24 |
—
|
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: 2006-08-24 | Statement: [Ceres, dwarfPlanetDesignationDate, 2006-08-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dwarfPlanetDesignationDate Context triple: [Ceres, dwarfPlanetDesignationDate, 2006-08-24]
-
A.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
B.
minorPlanetNumber
Indicates the unique numerical designation assigned to a minor planet within the catalog of such celestial bodies.
-
C.
hasDwarfPlanet
Indicates that one entity possesses or is associated with a dwarf planet as part of its system or domain.
-
D.
hasAsteroidNamedAfter
Indicates that an asteroid has been officially named in honor of a particular entity.
-
E.
discoveryDate
Indicates the date on which something was first discovered or identified.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c3f7b48190a31308bdc09817c6 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.