Triple
T20099519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Munmu |
E496495
|
entity |
| Predicate | posthumousName |
P744
|
FINISHED |
| Object |
Munmu-wang
Munmu-wang was a 7th-century king of the Korean kingdom of Silla, renowned for completing the unification of most of the Korean Peninsula.
|
E1411005
|
NE FINISHED |
How this triple was built (4 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: Munmu-wang | Statement: [King Munmu, posthumousName, Munmu-wang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Munmu-wang Context triple: [King Munmu, posthumousName, Munmu-wang]
-
A.
Punmu
Punmu is a remote Aboriginal community in Western Australia associated with the Martu people and their traditional desert lands.
-
B.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
-
C.
Nam-ku
Nam-ku is the McCune–Reischauer romanization of Nam District, an administrative district in the city of Busan, South Korea.
-
D.
Queen Inmok
Queen Inmok was a Joseon dynasty queen consort known for her political victimization during the factional struggles of late King Seonjo’s reign and the Gwanghaegun era.
-
E.
Baedal Minjok
Baedal Minjok is a leading South Korean food delivery platform and app known for its dominant market presence and distinctive branding.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Munmu-wang Triple: [King Munmu, posthumousName, Munmu-wang]
Generated description
Munmu-wang was a 7th-century king of the Korean kingdom of Silla, renowned for completing the unification of most of the Korean Peninsula.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Munmu-wang Target entity description: Munmu-wang was a 7th-century king of the Korean kingdom of Silla, renowned for completing the unification of most of the Korean Peninsula.
-
A.
Punmu
Punmu is a remote Aboriginal community in Western Australia associated with the Martu people and their traditional desert lands.
-
B.
Hyeonreung
Hyeonreung is a royal tomb from Korea’s Joseon Dynasty, notable as one of the UNESCO-listed burial sites of its kings and queens.
-
C.
Nam-ku
Nam-ku is the McCune–Reischauer romanization of Nam District, an administrative district in the city of Busan, South Korea.
-
D.
Queen Inmok
Queen Inmok was a Joseon dynasty queen consort known for her political victimization during the factional struggles of late King Seonjo’s reign and the Gwanghaegun era.
-
E.
Baedal Minjok
Baedal Minjok is a leading South Korean food delivery platform and app known for its dominant market presence and distinctive branding.
- F. None of above. chosen
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08270edd6481909230ece4487f93fd |
completed | May 16, 2026, 8:13 a.m. |
| NEDg | Description generation | batch_6a0827c6a68c8190aed2d531b4fd2030 |
completed | May 16, 2026, 8:16 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08288d98fc8190a146f43a027682f0 |
completed | May 16, 2026, 8:19 a.m. |
Created at: April 11, 2026, 11:26 p.m.