Triple
T29983696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Гжатский уезд |
E761666
|
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 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.
-
B.
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.
-
C.
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.
-
D.
административный центр субъекта Российской Федерации
Административный центр субъекта Российской Федерации — это населённый пункт, в котором расположены высшие органы государственной власти и управления данного субъекта РФ.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:35 p.m.