Triple
T6313836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctica |
E141566
|
entity |
| Predicate | temperatureRecord |
P2974
|
FINISHED |
| Object | below −80 °C in interior locations |
—
|
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: below −80 °C in interior locations | Statement: [East Antarctica, temperatureRecord, below −80 °C in interior locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureRecord Context triple: [East Antarctica, temperatureRecord, below −80 °C in interior locations]
-
A.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
-
B.
averageTemperature
Indicates the typical or mean temperature value associated with an entity over a specified period or context.
-
C.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
D.
recordedTemperatureRegion
chosen
Indicates that a particular temperature measurement was recorded for or associated with a specific geographic region.
-
E.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064a075dc8190acf7ec010cb4b00c |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.