Triple
T7384402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Wu |
E170344
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 吳 |
E66200
|
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: [Eastern Wu, nativeName, 吳]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 吳 Context triple: [Eastern Wu, nativeName, 吳]
-
A.
陳
陳 is a common Chinese surname and character with historical roots, widely used across Chinese-speaking communities and often romanized as "Chan," "Chen," or similar variants.
-
B.
苏
苏 is the standard Chinese abbreviation used to refer to Jiangsu Province in eastern China.
-
C.
Wu
chosen
Wu is a common Chinese surname borne by many notable individuals across politics, academia, entertainment, and sports.
-
D.
趙
趙 is a common Chinese surname with historical roots in ancient China, notably associated with the State of Zhao during the Warring States period.
-
E.
Liu Cunhou
Liu Cunhou was a Chinese military officer and warlord associated with the Yunnan clique during the early Republican era.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1efe1308190b96eefbff56140be |
completed | March 27, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802e23714819094a1b31c82a27fee |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:08 p.m.