Triple
T4756699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haumea family |
E105605
|
entity |
| Predicate | hasTypicalEccentricityRange |
P20350
|
FINISHED |
| Object | about 0.10–0.20 |
—
|
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: about 0.10–0.20 | Statement: [Haumea family, hasTypicalEccentricityRange, about 0.10–0.20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEccentricityRange Context triple: [Haumea family, hasTypicalEccentricityRange, about 0.10–0.20]
-
A.
hasEccentricity
Indicates that an object or orbit possesses a specific degree of deviation from being perfectly circular, quantified by its eccentricity value.
-
B.
orbitalEccentricity
chosen
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
C.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
D.
hasTypicalVelocity
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
E.
hasTypicalColumnHeightToDiameterRatio
Indicates that there is a characteristic or commonly observed proportional relationship between a column’s height and its diameter.
- 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.