Triple
T22471381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hwanghae Province |
E555509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative division of 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: former administrative division of Korea Context triple: [Hwanghae Province, instanceOf, former administrative division of Korea]
-
A.
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.
-
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.
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.
-
D.
one of the Three Kingdoms of Korea
One of the Three Kingdoms of Korea is a major ancient Korean state—Goguryeo, Baekje, or Silla—that existed between the 1st century BCE and 7th century CE and played a central role in shaping early Korean history, culture, and territorial formation.
-
E.
former district of Japan
A former district of Japan is an administrative subdivision that once existed within a prefecture but has since been dissolved or merged due to municipal reorganization.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.