Triple
T23407960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyeongchang County government |
E559986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county-level administrative authority |
C5679
|
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: county-level administrative authority Context triple: [Pyeongchang County government, instanceOf, county-level administrative authority]
-
A.
county-level jurisdiction
A county-level jurisdiction is an administrative division within a state or country that governs a specific geographic area, providing local services, regulations, and governance below the state or provincial level.
-
B.
county government
chosen
A county government is a local administrative body responsible for providing regional services, enforcing laws, managing public resources, and implementing policies within a defined county jurisdiction.
-
C.
county government agency
A county government agency is a local public organization responsible for administering specific services, regulations, and programs within a county’s jurisdiction on behalf of the county government.
-
D.
county government facility
A county government facility is a building or complex where local county officials and departments conduct administrative, legislative, and public service functions for residents within the county’s jurisdiction.
-
E.
borough-level jurisdiction
A borough-level jurisdiction is an administrative division within a larger city or region that possesses localized governmental authority and responsibilities specific to that borough.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:38 p.m.