Triple
T20099522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Munmu |
E496495
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 문무왕 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 문무왕 | Statement: [King Munmu, nativeName, 문무왕]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 문무왕 Context triple: [King Munmu, nativeName, 문무왕]
-
A.
문무왕
chosen
문무왕은 삼국 통일을 완수하고 신라의 전성기를 연 통일신라 초대 왕이다.
-
B.
King Heungdeok
King Heungdeok was a monarch of Korea’s Unified Silla period, remembered for efforts to stabilize royal authority and manage internal aristocratic power struggles.
-
C.
Kyonghung
Kyonghung is a town and county-level city in northeastern North Korea, located near the border with China in North Hamgyong Province.
-
D.
Gwangmu
Gwangmu was the era name associated with Emperor Gojong’s reign during Korea’s transition from the Joseon dynasty to the Korean Empire in the late 19th and early 20th centuries.
-
E.
King Munjong of Joseon
King Munjong of Joseon was the short-reigning fifth monarch of Korea’s Joseon dynasty, known for his scholarly background and for succeeding his father, King Sejong the Great.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666f2298819089659f13556ca305 |
completed | April 20, 2026, 5:46 p.m. |
Created at: April 11, 2026, 11:26 p.m.