Triple
T20454118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gongyang of Goryeo |
E501730
|
entity |
| Predicate | regnalName |
P744
|
FINISHED |
| Object | Gongyang |
—
|
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: Gongyang | Statement: [Gongyang of Goryeo, regnalName, Gongyang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gongyang Context triple: [Gongyang of Goryeo, regnalName, Gongyang]
-
A.
Gongyang
chosen
Gongyang was the last king of Korea’s Goryeo dynasty, whose reign marked the end of Goryeo and the rise of the Joseon dynasty.
-
B.
Gongdi
Gongdi is the posthumous temple name of Emperor Gong of the Sui dynasty, a short-reigning Chinese emperor during the dynasty’s final decline.
-
C.
Gongjin
Gongjin is the courtesy name of Zhou Yu, a renowned Eastern Han dynasty military general and strategist best known for his role in the Battle of Red Cliffs.
-
D.
Yongyan
Yongyan was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
E.
Gwan Gyeong
Gwan Gyeong was a historical Korean scholar-official known for helping compile the Samguk Sagi, one of the oldest surviving chronicles of Korea’s Three Kingdoms period.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d04ca4081909b428c31d16fca10 |
completed | April 20, 2026, 8:31 p.m. |
Created at: April 16, 2026, 11:32 a.m.