Triple
T23344592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UV Ceti |
E591821
|
entity |
| Predicate | effectiveTemperature_approx |
P57025
|
FINISHED |
| Object | ~2700 K |
—
|
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: ~2700 K | Statement: [UV Ceti, effectiveTemperature_approx, ~2700 K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveTemperature_approx Context triple: [UV Ceti, effectiveTemperature_approx, ~2700 K]
-
A.
temperatureRelativeToSurroundings
Indicates how an entity’s temperature compares to that of its immediate surroundings (e.g., warmer, cooler, or equal).
-
B.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
C.
hasEffectiveTemperature
chosen
Indicates that an entity (typically a star or other astronomical object) possesses a specific effective surface temperature characterizing its emitted radiation.
-
D.
equilibriumTemperature
Indicates the temperature at which a system’s heat exchange balances so that no net change in its thermal state occurs.
-
E.
temperatureProportionalTo
Indicates that the temperature of one entity changes in direct proportion to the temperature of another entity.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198358fb8819094c74cfd53cbab44 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.