Triple
T1688032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeonje District |
E36486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Autonomous District of South Korea |
C11161
|
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: Autonomous District of South Korea Context triple: [Yeonje District, instanceOf, Autonomous District of South Korea]
-
A.
Autonomous district of South Korea
chosen
An autonomous district of South Korea is a self-governing municipal subdivision within a metropolitan city or special city that has its own local government and administrative authority over local affairs.
-
B.
province of South Korea
A province of South Korea is a primary administrative division of the country, governed by a provincial government that oversees regional affairs, services, and development across multiple cities and counties.
-
C.
Koreatown
Koreatown is an urban neighborhood characterized by a high concentration of Korean residents, businesses, and cultural institutions that serve as a hub for Korean culture and community life outside of Korea.
-
D.
special city in South Korea
A special city in South Korea is a top-level administrative division that functions as a city with the same status as a province, directly governed by the central government and typically encompassing a large urban area.
-
E.
autonomous prefecture
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.