Triple
T19361217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Site No. 124 of South Korea |
E484283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Historic Site of South Korea |
C41989
|
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: Historic Site of South Korea Context triple: [Historic Site No. 124 of South Korea, instanceOf, Historic Site of South Korea]
-
A.
national treasure of South Korea
A national treasure of South Korea is a cultural property officially designated by the government as having exceptional historical, artistic, or academic value, warranting the highest level of protection and preservation.
-
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.
special city in South Korea
A special city in South Korea is a top-level administrative division that functions as a city with the same status as a province, directly governed by the central government and typically encompassing a large urban area.
-
D.
Korean historical document
A Korean historical document is an original written or printed record produced in or about Korea’s past, preserving information on its political, social, cultural, or intellectual history.
-
E.
city in South Korea
A city in South Korea is an urban administrative division governed by local authorities, characterized by concentrated population, infrastructure, and economic, cultural, and social activities within the Republic of Korea.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:34 p.m.