Triple
T23721529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Югорский Шар |
E586155
|
entity |
| Predicate | климатическийПояс |
P77118
|
FINISHED |
| Object | арктический пояс |
—
|
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: арктический пояс | Statement: [Югорский Шар, климатическийПояс, арктический пояс]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: климатическийПояс Context triple: [Югорский Шар, климатическийПояс, арктический пояс]
-
A.
climatologicalRegion
chosen
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
B.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
-
C.
climatologicalType
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
D.
climaticRole
Indicates the role or influence that something has on climate patterns or climatic conditions.
-
E.
isClimaticContrastWith
Indicates that two entities differ significantly in climate characteristics, such as temperature, precipitation, or seasonal patterns, in a way that highlights a notable contrast.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:01 p.m.