Triple
T36066535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belorussian Military District |
E1043246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territorial-administrative formation |
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: territorial-administrative formation Context triple: [Belorussian Military District, instanceOf, territorial-administrative formation]
-
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.
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.
-
C.
territorial state
A territorial state is a political entity that exercises sovereign authority over a clearly defined geographic area and the population within its borders.
-
D.
ethnic territory
An ethnic territory is a geographically defined area predominantly inhabited by a particular ethnic group, where shared cultural, linguistic, or historical traits form the basis of collective identity and claims to space.
-
E.
administrative formation
An administrative formation is an organized territorial or institutional unit established by a governing authority to manage public administration, implement policies, and provide services within a defined jurisdiction.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.