Triple
T4756682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haumea family |
E105605
|
entity |
| Predicate | hasOrbitalCharacteristic |
P58578
|
FINISHED |
| Object | similar semi-major axes among members |
—
|
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: similar semi-major axes among members | Statement: [Haumea family, hasOrbitalCharacteristic, similar semi-major axes among members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrbitalCharacteristic Context triple: [Haumea family, hasOrbitalCharacteristic, similar semi-major axes among members]
-
A.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
hasOrbitalStability
Indicates that an object maintains a stable, non-disruptive orbit around another body over time.
-
C.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
D.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
E.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
- 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_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. |
| PDg | Predicate description generation | batch_69bd6424a1d08190ac1d5fc574dc1b55 |
completed | March 20, 2026, 3:13 p.m. |
Created at: March 20, 2026, 1:20 p.m.