Triple
T18714444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | თერგი |
E457598
|
entity |
| Predicate | განლაგებულია რეგიონში |
P41898
|
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.
compiledInRegion
Indicates that a software artifact was compiled within a specific geographic or logical region.
-
B.
linkedToRegion
chosen
Indicates that one entity is associated or connected to a specific geographic or administrative region.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
endsInRegion
Indicates that an entity’s spatial or temporal extent terminates within the boundaries of a specified region.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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.