Triple
T26747271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icehotel in Jukkasjärvi |
E674433
|
entity |
| Predicate | temperatureInside |
P4459
|
FINISHED |
| Object | around −5 °C to −8 °C |
—
|
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: around −5 °C to −8 °C | Statement: [Icehotel in Jukkasjärvi, temperatureInside, around −5 °C to −8 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureInside Context triple: [Icehotel in Jukkasjärvi, temperatureInside, around −5 °C to −8 °C]
-
A.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
B.
hasTemperature
chosen
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
temperatureChange
Indicates a change in temperature between two states, times, or conditions, specifying how much and in which direction the temperature has varied.
-
D.
temperatureRelativeToSurroundings
Indicates how an entity’s temperature compares to that of its immediate surroundings (e.g., warmer, cooler, or equal).
-
E.
temper
Indicates moderating, softening, or counterbalancing the intensity, effect, or quality of something through the influence of something else.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6188630dc8190ba0602ebe2b3ab6b |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:52 a.m.