Triple
T12501315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanover Region |
E298829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district-level administrative region |
C4246
|
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: district-level administrative region Context triple: [Hanover Region, instanceOf, district-level administrative region]
-
A.
District
chosen
A District is a defined geographic or administrative area within a larger region, established for governance, organization, or service delivery purposes.
-
B.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
-
C.
district office
A district office is a local administrative center that manages and coordinates government or organizational services, operations, and support within a specific geographic district.
-
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.
district-level people’s committee
A district-level people’s committee is a local executive governing body responsible for implementing laws, policies, and administrative decisions within a specific district under the authority of higher-level state institutions.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.