Triple
T26215128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buk-gu Office |
E655600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district-level administrative body |
C20571
|
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 body Context triple: [Buk-gu Office, instanceOf, district-level administrative body]
-
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 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
chosen
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.
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.
-
E.
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.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:54 p.m.