Triple
T4756685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haumea family |
E105605
|
entity |
| Predicate | hasSurfaceProperty |
P44361
|
FINISHED |
| Object | water-ice-rich spectra |
—
|
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: water-ice-rich spectra | Statement: [Haumea family, hasSurfaceProperty, water-ice-rich spectra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceProperty Context triple: [Haumea family, hasSurfaceProperty, water-ice-rich spectra]
-
A.
hasSurfaceBody
Indicates that one entity possesses or is characterized by a particular surface or outer body.
-
B.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
D.
hasSurfaceComposition
chosen
Indicates that one entity has a surface made up of, or characterized by, the material or composition specified by another entity.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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.