Triple
T28249073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 244 |
E712265
|
entity |
| Predicate | effectiveTemperaturePrimary_K |
P57025
|
FINISHED |
| Object | about 9900 |
—
|
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: about 9900 | Statement: [Gliese 244, effectiveTemperaturePrimary_K, about 9900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveTemperaturePrimary_K Context triple: [Gliese 244, effectiveTemperaturePrimary_K, about 9900]
-
A.
hasEffectiveTemperature
chosen
Indicates that an entity (typically a star or other astronomical object) possesses a specific effective surface temperature characterizing its emitted radiation.
-
B.
equilibriumTemperature
Indicates the temperature at which a system’s heat exchange balances so that no net change in its thermal state occurs.
-
C.
characteristicTemperatureScale
Indicates the temperature scale (e.g., Celsius, Fahrenheit, Kelvin) that is used as the standard or defining measure for a given entity or context.
-
D.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
E.
surfaceTemperature_K
Indicates the temperature of a surface expressed in kelvins.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 11:03 p.m.