Triple
T20553155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Jangsu |
E504647
|
entity |
| Predicate | movedCapitalFrom |
P25378
|
FINISHED |
| Object | Gungnae-seong |
—
|
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: Gungnae-seong | Statement: [King Jangsu, movedCapitalFrom, Gungnae-seong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gungnae-seong Context triple: [King Jangsu, movedCapitalFrom, Gungnae-seong]
-
A.
Gungnae-seong
chosen
Gungnae-seong was the fortified capital city of the ancient Korean kingdom of Goguryeo, serving as a key political and military center.
-
B.
Hongneung
Hongneung is a royal tomb site in South Korea that serves as the burial place of Emperor Gojong of Korea.
-
C.
Nyeongneung
Nyeongneung is a royal tomb in South Korea that forms part of the UNESCO-listed cluster of Joseon Dynasty royal burial sites.
-
D.
Yeongneung
Yeongneung is a royal tomb complex in Yeoju, South Korea, that houses the burial site of King Sejong the Great and is part of the UNESCO-listed Royal Tombs of the Joseon Dynasty.
-
E.
Yeongneung
Yeongneung is a royal tomb site in Paju, South Korea, known as the burial place of King Jinjong and Queen Hyosun of the Joseon Dynasty.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5db052c8190801e53f6148113c8 |
completed | April 20, 2026, 10:16 p.m. |
Created at: April 16, 2026, 11:38 a.m.