Triple
T14130532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yang Dezhi |
E350151
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Dezhi |
E365414
|
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: Dezhi | Statement: [Yang Dezhi, givenName, Dezhi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dezhi Context triple: [Yang Dezhi, givenName, Dezhi]
-
A.
Dezhi
chosen
Dezhi is the courtesy name of the Xuande Emperor, a Ming dynasty ruler of China known for his relatively stable and prosperous reign in the early 15th century.
-
B.
Deyu
Deyu is the courtesy name of the Hongguang Emperor, a short-lived Southern Ming ruler who attempted to restore the Ming dynasty after the fall of Beijing to the Qing.
-
C.
Dezong
Dezong is the posthumous temple name of the Guangxu Emperor, a late Qing dynasty ruler of China.
-
D.
Dongsheng
Dongsheng is a Chinese given name commonly used for males.
-
E.
Dunhua
Dunhua is a county-level city in northeastern China's Jilin Province, known for its location within the Yanbian Korean Autonomous Prefecture and its mix of Han and Korean cultural influences.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf10e3948190b21968bc39094a8e |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:47 p.m.