Triple
T23317883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldebaran B |
E590759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suspected substellar companion |
C41598
|
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: suspected substellar companion Context triple: [Aldebaran B, instanceOf, suspected substellar companion]
-
A.
substellar companion
chosen
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.
-
B.
stellar companion
A stellar companion is a star that orbits or co-orbits with another star, forming a gravitationally bound multiple-star system such as a binary or higher-order configuration.
-
C.
spectroscopic binary candidate
A spectroscopic binary candidate is a star system suspected to contain two orbiting stars based on variations or duplications in its spectral lines, but lacking sufficient data for definitive confirmation.
-
D.
companion star
A companion star is a secondary star gravitationally bound to a primary star, often forming a binary or multiple star system and influencing its partner’s evolution and observable properties.
-
E.
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.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.