Triple
T23721926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rason |
E586167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of North Korea |
C15697
|
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 North Korea Context triple: [Rason, instanceOf, administrative division of North Korea]
-
A.
province of North Korea
chosen
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.
-
B.
state organ of North Korea
A state organ of North Korea is an official governmental body or institution that exercises political, administrative, legislative, judicial, or military authority under the centralized control of the ruling Workers’ Party of Korea.
-
C.
administrative division of Japan
An administrative division of Japan is a geographically defined area, such as a prefecture, municipality, or special ward, established by the government to organize local governance, public administration, and the delivery of services.
-
D.
division of the Korean People's Army
A division of the Korean People's Army is a large, combined-arms military formation typically composed of several regiments and support units, organized to conduct sustained ground combat operations under the command of the KPA.
-
E.
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.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:04 p.m.