Triple
T35506579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcus |
E1026164
|
entity |
| Predicate | minorPlanetDesignation |
P175319
|
FINISHED |
| Object | (90482) Orcus |
—
|
NE NERFINISHED |
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: (90482) Orcus | Statement: [Orcus, minorPlanetDesignation, (90482) Orcus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorPlanetDesignation Context triple: [Orcus, minorPlanetDesignation, (90482) Orcus]
-
A.
minorPlanetGroup
Indicates that a minor planet belongs to a specific dynamical or classification group of minor planets.
-
B.
isMinorPlanet
Indicates that the subject is classified as a minor planet (such as an asteroid or dwarf planet) rather than a major planet or other type of celestial object.
-
C.
minorPlanetNumber
Indicates the unique numerical designation assigned to a minor planet within the catalog of such celestial bodies.
-
D.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
-
E.
hasMinorPlanetCenterDesignation
chosen
Indicates that an entity is assigned an official designation by the Minor Planet Center (e.g., for asteroids or other small Solar System bodies).
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.