Triple
T28388873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Government of Shapingba District |
E719095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district people's government |
C19792
|
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 people's government Context triple: [People's Government of Shapingba District, instanceOf, district people's government]
-
A.
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.
-
B.
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.
-
C.
district administration
chosen
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.
-
D.
rural administrative district
A rural administrative district is a defined geographic area outside urban centers that is governed as a single unit for local administration, services, and regulation of predominantly agricultural or sparsely populated communities.
-
E.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:12 a.m.