Triple
T24678870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ლაგოდეხი |
E611067
|
entity |
| Predicate | გეოგრაფიული რეგიონი |
P64798
|
FINISHED |
| Object | კახეთის ალაზნის ველი |
—
|
NE NERFINISHED |
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.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
B.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
C.
geopoliticalRegion
Indicates a relationship where an entity is a defined political or administrative geographic area, such as a country, state, province, or similar region.
-
D.
წყარო_რეგიონი
Indicates a relationship where something originates from, is sourced in, or comes out of a particular region.
-
E.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:08 a.m.