Triple
T20479376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1000 Piazzia |
E502409
|
entity |
| Predicate | minorPlanetGroup |
P140259
|
FINISHED |
| Object | main-belt asteroids |
—
|
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 asteroids | Statement: [1000 Piazzia, minorPlanetGroup, main-belt asteroids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorPlanetGroup Context triple: [1000 Piazzia, minorPlanetGroup, main-belt asteroids]
-
A.
minorPlanetNumber
Indicates the unique numerical designation assigned to a minor planet within the catalog of such celestial bodies.
-
B.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
C.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
D.
hasAsteroidNamedAfter
Indicates that an asteroid has been officially named in honor of a particular entity.
-
E.
planetDesignation
Indicates the formal naming or labeling assigned to a planet within a particular cataloging or classification system.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:34 a.m.