Triple
T11526531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Army units operating near Suomussalmi |
E273308
|
entity |
| Predicate | temperatureConditions |
P99538
|
FINISHED |
| Object | extreme cold |
—
|
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: extreme cold | Statement: [Red Army units operating near Suomussalmi, temperatureConditions, extreme cold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureConditions Context triple: [Red Army units operating near Suomussalmi, temperatureConditions, extreme cold]
-
A.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
B.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
temperatureChange
Indicates a change in temperature between two states, times, or conditions, specifying how much and in which direction the temperature has varied.
-
E.
temperatureDependent
Indicates that the existence, intensity, or outcome of a relationship or process varies as a function of temperature.
- F. None of above. chosen
Provenance (4 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd379648190b342e0c4b4f685b7 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.