Triple
T31768881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeong Do-jeon |
E810883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Joseon dynasty politician |
C57587
|
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 politician Context triple: [Jeong Do-jeon, instanceOf, Joseon dynasty politician]
-
A.
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.
-
B.
Song dynasty politician
A Song dynasty politician is an official who served in the governmental and bureaucratic structures of China’s Song dynasty, influencing administration, policy, and state affairs.
-
C.
member of the Joseon dynasty
A member of the Joseon dynasty is an individual belonging to the royal or collateral family line that ruled Korea from 1392 to 1897, participating in its political, social, and cultural life according to strict Confucian hierarchies.
-
D.
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.
-
E.
Qin dynasty politician
A Qin dynasty politician was an official or statesman who served in the central or regional administration of the Qin state or empire (221–206 BCE), helping implement its legalist policies, bureaucratic reforms, and imperial governance.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:33 p.m.