Triple
T14486813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Yan |
E359249
|
entity |
| Predicate | titleInChinese |
P51900
|
FINISHED |
| Object | 燕王 |
E754206
|
NE FINISHED |
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: [Prince of Yan, titleInChinese, 燕王]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 燕王 Context triple: [Prince of Yan, titleInChinese, 燕王]
-
A.
King Daoxiang of Zhao
King Daoxiang of Zhao was a late Warring States period monarch of the Chinese state of Zhao, known for his efforts to maintain the kingdom’s strength amid rising pressure from the Qin state.
-
B.
上皇
上皇は日本において天皇が退位した後に名乗る称号で、現役の天皇とは区別される前天皇の身分を指す。
-
C.
King Youmiu of Zhao
King Youmiu of Zhao was a monarch of the Warring States–period Chinese state of Zhao, remembered as one of its later rulers during the decline of the state.
-
D.
King Zhao of Yan
chosen
King Zhao of Yan was a Warring States period ruler of the ancient Chinese state of Yan, known for his efforts to strengthen the state and for employing the famous general Yue Yi in campaigns against Qi.
-
E.
趙
趙 is a common Chinese surname with historical roots in ancient China, notably associated with the State of Zhao during the Warring States period.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd64a925148190992101984895a20b |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:20 a.m.