Triple
T32903089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German–Korean Forum |
E841662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Germany–South Korea relations organization |
C60765
|
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: Germany–South Korea relations organization Context triple: [German–Korean Forum, instanceOf, Germany–South Korea relations organization]
-
A.
South Korean public organization
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.
EU–Japan relations mechanism
The EU–Japan relations mechanism is the institutional and procedural framework through which the European Union and Japan coordinate policies, negotiate agreements, and manage their political, economic, and security cooperation.
-
C.
dong of South Korea
A dong of South Korea is the smallest administrative neighborhood unit within a city or district, responsible for local governance and community services.
-
D.
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.
-
E.
Korean official
A Korean official is a government-appointed or elected public servant in Korea responsible for implementing laws, administering public policy, and representing state authority within their designated jurisdiction or office.
- F. None of above. chosen
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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.