Triple
T20326727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/2015 (136472) 1 |
E492357
|
entity |
| Predicate | hostBodyMinorPlanetNumber |
P66743
|
FINISHED |
| Object | 136472 |
—
|
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: 136472 | Statement: [S/2015 (136472) 1, hostBodyMinorPlanetNumber, 136472]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostBodyMinorPlanetNumber Context triple: [S/2015 (136472) 1, hostBodyMinorPlanetNumber, 136472]
-
A.
minorPlanetNumber
Indicates the unique numerical designation assigned to a minor planet within the catalog of such celestial bodies.
-
B.
hasParentBodyMinorPlanetNumber
chosen
Indicates that one entity is associated with the minor planet number assigned to its parent celestial body.
-
C.
hipparcosNumber
Indicates the identifier assigned to a star in the Hipparcos astrometric catalog.
-
D.
primaryMirrorDesignation
Indicates that one entity is designated as the primary mirror (main reflective component) associated with another entity.
-
E.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e4130081909ec54f131939e442 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.