Triple
T23371978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Матуа |
E593498
|
entity |
| Predicate | имеетКлимат |
P193
|
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.
hasClimate
chosen
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
B.
hasClimateContext
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
-
C.
climatologicalType
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
D.
climateBetween
Indicates that something (such as a location, period, or condition) has a climate that lies within a specified range or intermediate state between two other climatic conditions.
-
E.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.