Triple
T24781075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
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.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
E.
climateSubgroup
Indicates that one climate category is a more specific subgroup or subtype within another, broader climate category.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d67a208190909034a085b20b59 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:44 a.m.