Triple
T5565934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Special City |
E145879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of South Korea |
C2248
|
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: administrative division of South Korea Context triple: [Seoul Special City, instanceOf, administrative division of South Korea]
-
A.
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.
-
B.
Autonomous district of South Korea
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.
-
C.
province of North Korea
A province of North Korea is a primary administrative division of the country, governed by local authorities under the central government and encompassing multiple cities, counties, and rural areas.
-
D.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
E.
first-level administrative division of the Philippines
A first-level administrative division of the Philippines is a primary local government unit, such as a province, highly urbanized city, or independent component city, directly under the national government and above municipalities and barangays in the administrative hierarchy.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.