Triple
T25609977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir Oblast authorities |
E642020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional government authorities |
C25857
|
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: regional government authorities Context triple: [Vladimir Oblast authorities, instanceOf, regional government authorities]
-
A.
regional government service
A regional government service is an administrative entity that delivers public programs, resources, and regulatory functions within a specific geographic area under the authority of a higher-level government.
-
B.
provincial authority
A provincial authority is a regional governing body responsible for administering laws, policies, and public services within a specific province under a broader national framework.
-
C.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
D.
territorial government agency
A territorial government agency is a public organization established by a territorial authority to administer laws, deliver services, and manage resources within a defined geographic area.
-
E.
sub‑national government
chosen
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:40 p.m.