Triple
T4756659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiʻiaka ring |
E105604
|
entity |
| Predicate | isDebrisFrom |
P22854
|
FINISHED |
| Object | Haumea system material |
—
|
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: Haumea system material | Statement: [Hiʻiaka ring, isDebrisFrom, Haumea system material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDebrisFrom Context triple: [Hiʻiaka ring, isDebrisFrom, Haumea system material]
-
A.
debrisFieldStates
Indicates the various conditions or statuses associated with a particular debris field over time or in a given context.
-
B.
debrisRecoveryEffort
Indicates efforts or actions undertaken to locate, collect, and secure debris resulting from an incident or event.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
tidalDebris
chosen
Indicates material that has been gravitationally stripped from an astronomical object and dispersed into space by tidal forces.
-
E.
isCombatDecoration
Indicates that an award or decoration is specifically given for participation or valor in combat or military conflict.
- 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.