Triple
T18714483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | თერგი |
E457598
|
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.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
-
B.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
C.
climatologicalRegion
chosen
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
D.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab4ee6881908f19558937cbb078 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.