Triple
T36656285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choeup-dong |
E904997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood-level administrative district |
C23950
|
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: neighborhood-level administrative district Context triple: [Choeup-dong, instanceOf, neighborhood-level administrative district]
-
A.
commune-level administrative unit
chosen
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
-
B.
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.
-
C.
territorial district
A territorial district is a defined geographic area within a larger region or country, established for administrative, political, legal, or organizational purposes.
-
D.
administrativeDistrictName
The administrativeDistrictName class represents the official name assigned to a specific administrative district within a governmental or organizational territorial hierarchy.
-
E.
administrative community
An administrative community is a group of individuals and organizations connected through shared governance structures, procedures, and responsibilities for managing and implementing policies or services within a defined domain.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.