Triple
T23317900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldebaran B |
E590759
|
entity |
| Predicate | hasHostStarType |
P42135
|
FINISHED |
| Object | K-type giant (Aldebaran) |
—
|
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: K-type giant (Aldebaran) | Statement: [Aldebaran B, hasHostStarType, K-type giant (Aldebaran)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostStarType Context triple: [Aldebaran B, hasHostStarType, K-type giant (Aldebaran)]
-
A.
hasCentralStarType
Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
-
B.
containsExoplanetHostStars
Indicates that the subject set or collection includes stars that are known to host one or more exoplanets.
-
C.
hostStarType
chosen
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
D.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
E.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197828c408190ae071624e40de4cc |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.