Triple
T20675764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok Station |
E508154
|
entity |
| Predicate | recordedTemperatureDate |
P86046
|
FINISHED |
| Object | 21 July 1983 |
—
|
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: 21 July 1983 | Statement: [Vostok Station, recordedTemperatureDate, 21 July 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedTemperatureDate Context triple: [Vostok Station, recordedTemperatureDate, 21 July 1983]
-
A.
recordedSurfaceTemperaturePeriod
Indicates the time span over which a surface temperature measurement was recorded.
-
B.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
-
C.
recordedTemperatureRegion
Indicates that a particular temperature measurement was recorded for or associated with a specific geographic region.
-
D.
recordedOnDate
chosen
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
E.
measuredAt
Indicates the time or point at which a measurement was taken or recorded for an entity or event.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5cf18b48190be6995e197946517 |
completed | April 20, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.