Triple
T35811568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მცხეთა-მთიანეთის რეგიონი |
E1035242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ადმინისტრაციულ-ტერიტორიული ერთეული |
C740
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ადმინისტრაციულ-ტერიტორიული ერთეული Context triple: [მცხეთა-მთიანეთის რეგიონი, instanceOf, ადმინისტრაციულ-ტერიტორიული ერთეული]
-
A.
administrative union
An administrative union is a collaborative arrangement in which multiple governmental or administrative entities share certain functions, services, or governance structures while retaining their individual legal identities.
-
B.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
C.
Verwaltungseinheit
Eine Verwaltungseinheit ist eine organisatorische Einheit innerhalb einer öffentlichen oder privaten Institution, die für die Erfüllung bestimmter Verwaltungsaufgaben und die Umsetzung von Richtlinien in einem abgegrenzten Zuständigkeitsbereich verantwortlich ist.
-
D.
federal unit
A federal unit is a constituent political entity, such as a state or province, within a federal system that shares sovereignty with a central government while retaining certain autonomous powers.
-
E.
federal administrative unit
A federal administrative unit is a territorial or organizational subdivision within a federal state that carries out governmental functions and implements policies under the authority of the national government.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:06 p.m.