Triple
T13469890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunwen |
E311599
|
entity |
| Predicate | styleName |
P39478
|
FINISHED |
| Object | Yunwen |
E311599
|
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: Yunwen | Statement: [Yunwen, styleName, Yunwen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yunwen Context triple: [Yunwen, styleName, Yunwen]
-
A.
Yunwen
chosen
Yunwen was the personal name of the Jianwen Emperor, a Ming dynasty ruler of China known for his short and turbulent reign and subsequent mysterious disappearance.
-
B.
Yuanshuo
Yuanshuo was a regnal era during the reign of Emperor Wu of the Western Han dynasty in ancient China.
-
C.
Yuanzhong
Yuanzhong was the courtesy name of Cao Rui, the second emperor of the state of Cao Wei during China’s Three Kingdoms period.
-
D.
Yingchao
Yingchao is the given name of Deng Yingchao, a prominent Chinese revolutionary leader and influential politician in the 20th century.
-
E.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d8ab8548190a0a1adbe927c95d0 |
completed | May 3, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.