Triple
T5690827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunminjeongeum |
E125423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national treasure of South Korea |
C18617
|
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: national treasure of South Korea Context triple: [Hunminjeongeum, instanceOf, national treasure of South Korea]
-
A.
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.
-
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.
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.
-
D.
Korean king
A Korean king is the sovereign ruler of a Korean dynasty, responsible for governing the kingdom, upholding Confucian ideals, overseeing military and diplomatic affairs, and serving as the symbolic and political head of state.
-
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. 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.