Triple
T35811877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | გარდაბანი |
E1035252
|
entity |
| Predicate | ადმინისტრაციული სტატუსი |
P71309
|
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.
administrativeStatusOfEntityRepresented
chosen
Indicates the current administrative or operational status assigned to the entity that is being represented.
-
B.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
C.
administeredAs
Indicates that one entity is given or applied to another entity as a treatment, dose, or intervention.
-
D.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
E.
governsStatus
Indicates that one entity has authoritative control or regulatory influence over the status or condition of 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.