Triple
T23188740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Canis Minoris |
E579669
|
entity |
| Predicate | isHotBlueWhiteStar |
P146438
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beta Canis Minoris, isHotBlueWhiteStar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHotBlueWhiteStar Context triple: [Beta Canis Minoris, isHotBlueWhiteStar, true]
-
A.
isBlueGiantStar
chosen
Indicates that the subject is a star classified as a blue giant, characterized by high temperature, large size, and high luminosity.
-
B.
isBlueSupergiant
Indicates that the subject is a star classified as a blue supergiant, characterized by very high mass, temperature, and luminosity.
-
C.
isBrightGiant
Indicates that an entity is a very luminous star of large radius and high intrinsic brightness, typically classified as a bright giant in stellar taxonomy.
-
D.
isBrightStar
Indicates that the subject star has a high intrinsic luminosity or apparent brightness compared to typical stars.
-
E.
isSunLike
Indicates that one celestial object shares key physical and behavioral characteristics with the Sun, such as mass, temperature, luminosity, and spectral type.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd592248190a7e705c554885cd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.