Triple
T896255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haumea |
E19352
|
entity |
| Predicate | ringPlane |
P20823
|
FINISHED |
| Object | aligned with Haumea equator |
—
|
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: aligned with Haumea equator | Statement: [Haumea, ringPlane, aligned with Haumea equator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringPlane Context triple: [Haumea, ringPlane, aligned with Haumea equator]
-
A.
plane
Indicates that an entity is a flat, two-dimensional surface extending infinitely in all directions within its dimension.
-
B.
roundel
Indicates that one entity bears, displays, or is marked with a circular emblem or symbol representing another entity.
-
C.
involvesPlate
Indicates that an event, action, or situation includes or makes use of a plate as a relevant participant or object.
-
D.
floorPlan
Indicates that one entity serves as the architectural layout or room arrangement blueprint for another entity (such as a building or space).
-
E.
plateType
Indicates the specific category or style of plate associated with an item or context.
- F. None of above. chosen
Provenance (4 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad23d6e88190a2fb5e1e168a7b44 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.