Triple
T4756649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiʻiaka ring |
E105604
|
entity |
| Predicate | celestialBodyTypeOfPrimary |
P9991
|
FINISHED |
| Object | dwarf planet |
—
|
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: dwarf planet | Statement: [Hiʻiaka ring, celestialBodyTypeOfPrimary, dwarf planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialBodyTypeOfPrimary Context triple: [Hiʻiaka ring, celestialBodyTypeOfPrimary, dwarf planet]
-
A.
inSolarSystemBody
Indicates that one entity is located within, on, or as part of a specified solar system body (such as a planet, moon, or asteroid).
-
B.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
C.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
D.
majorBody
Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
-
E.
astronomicalType
chosen
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.