Triple
T30475180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Committee of District 1 |
E775423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district-level government body |
C26308
|
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 government body Context triple: [People's Committee of District 1, instanceOf, district-level government body]
-
A.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
B.
district-level people’s committee
chosen
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.
-
C.
district-level city
A district-level city is an administrative division in some countries, typically below a province or region, that governs both an urban center and its surrounding rural or suburban areas.
-
D.
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.
-
E.
cantonal government body
A cantonal government body is an official administrative and political institution that governs a canton, implementing regional laws, policies, and public services within its 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:11 p.m.