Triple
T9046486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oprichnina |
E216767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territorial-administrative division |
C536
|
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 division Context triple: [Oprichnina, instanceOf, territorial-administrative division]
-
A.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
B.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
C.
administrative division of Japan
An administrative division of Japan is a geographically defined area, such as a prefecture, municipality, or special ward, established by the government to organize local governance, public administration, and the delivery of services.
-
D.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
E.
former administrative territorial entity
chosen
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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:09 p.m.