Triple
T15803395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 趙 |
E383150
|
entity |
| Predicate | traditionalForm |
P24858
|
FINISHED |
| Object | 趙 |
E383150
|
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: [趙, traditionalForm, 趙]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 趙 Context triple: [趙, traditionalForm, 趙]
-
A.
趙
chosen
趙 is a common Chinese surname with historical roots in ancient China, notably associated with the State of Zhao during the Warring States period.
-
B.
晉
晉 is the Chinese name of the ancient State of Jin, a major feudal power during the Spring and Autumn period of Chinese history.
-
C.
Emperor Zhi of Han
Emperor Zhi of Han was a briefly reigning, child emperor of the Eastern Han dynasty whose short life and rule were overshadowed by the dominance of powerful regents and court factions.
-
D.
刘
刘 is a common Chinese surname and given name character, historically associated with several prominent clans and figures in Chinese history.
-
E.
蔣
蔣 is a common Chinese surname notably borne by historical figures such as Chiang Kai-shek.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b524835c8190ae286b2562f07756 |
completed | April 16, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff90b4fe5881909471887219654d69 |
completed | May 9, 2026, 7:53 p.m. |
Created at: April 10, 2026, 4:48 a.m.