Triple
T29295923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heungseon Daewongun |
E742828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Joseon Dynasty person |
C18267
|
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: Joseon Dynasty person Context triple: [Heungseon Daewongun, instanceOf, Joseon Dynasty person]
-
A.
Goryeo dynasty person
A Goryeo dynasty person is an individual who lived in or was significantly associated with Korea’s Goryeo dynasty (918–1392), contributing to its political, social, cultural, or historical developments.
-
B.
Korean king
chosen
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.
-
C.
Korean emperor
A Korean emperor is the supreme hereditary monarch who holds the highest sovereign authority over a unified Korean state, historically or in a conceptual context.
-
D.
Jin state ruler
A Jin state ruler is the sovereign leader of the ancient Chinese state of Jin, responsible for governing its territories, commanding its military, and managing its political and diplomatic affairs during the Zhou dynasty period.
-
E.
Joseon Dynasty military officer
A Joseon Dynasty military officer was a state-appointed commander responsible for organizing, training, and leading troops in defense of the Korean kingdom, enforcing royal authority, and maintaining regional security according to Confucian-based military hierarchies.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:06 p.m.