Triple
T37761189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581h |
E941276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disputed exoplanet candidate |
C65116
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: disputed exoplanet candidate Context triple: [Gliese 581h, instanceOf, disputed exoplanet candidate]
-
A.
transiting exoplanet candidate
A transiting exoplanet candidate is an astronomical object identified by periodic dips in a star’s brightness that suggest, but do not yet confirm, the presence of a planet passing in front of the star.
-
B.
disputed astronomical object
chosen
A disputed astronomical object is a celestial body whose nature, classification, or even existence is uncertain or contested within the scientific community.
-
C.
scattered disc object candidate
A scattered disc object candidate is a distant icy body in the outer Solar System whose highly eccentric and inclined orbit suggests it may belong to the scattered disc population but lacks sufficient observational data for definitive classification.
-
D.
substellar companion
A substellar companion is an astronomical object, such as a brown dwarf or massive planet, that orbits a star or stellar remnant but lacks sufficient mass to sustain hydrogen fusion like a true star.
-
E.
possible dwarf planet
A possible dwarf planet is a celestial body that is suspected to meet the criteria for dwarf planet status—orbiting the Sun, being nearly round in shape, and not having cleared its orbital neighborhood—but has not yet been officially classified as such.
- F. None of above.
Provenance (1 batch)
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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.