Triple
T23408097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCST |
E559989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Korean government agency |
C45449
|
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: South Korean government agency Context triple: [MCST, instanceOf, South Korean government agency]
-
A.
South Korean public organization
chosen
A South Korean public organization is a government-established or government-funded entity that delivers public services, implements national or local policies, and manages administrative or regulatory functions in South Korea.
-
B.
South Korean company
A South Korean company is a business entity legally registered and operating in South Korea, typically structured under its corporate laws and engaged in commercial, industrial, or service activities within domestic and global markets.
-
C.
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.
-
D.
Korean historical institution
A Korean historical institution is an organization or establishment rooted in Korea’s past that preserves, practices, or symbolizes traditional political, social, cultural, or educational systems and values.
-
E.
government agency of Japan
A government agency of Japan is an official administrative body established by the Japanese government to implement laws, deliver public services, and manage specific policy areas at the national level.
- 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.