Triple
T31664595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Demchugdongrub |
E808091
|
entity |
| Predicate | nameInChinese |
P4878
|
FINISHED |
| Object |
德穆楚克栋鲁普
德穆楚克栋鲁普是中国近现代史上一位蒙古族王公与政治人物,曾在日本扶植下担任蒙古联盟自治政府的领导者。
|
E1970715
|
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 Demchugdongrub, nameInChinese, 德穆楚克栋鲁普]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 德穆楚克栋鲁普 Triple: [Prince Demchugdongrub, nameInChinese, 德穆楚克栋鲁普]
Generated description
德穆楚克栋鲁普是中国近现代史上一位蒙古族王公与政治人物,曾在日本扶植下担任蒙古联盟自治政府的领导者。
Provenance (5 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aa2811a08190bd7adcf79e834c24 |
completed | May 3, 2026, 1:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79ee83f081909fd5ce49a5e717ff |
completed | June 12, 2026, 3:15 a.m. |
| NEDg | Description generation | batch_6a2b7ad82acc8190abb3d91b02dd8524 |
completed | June 12, 2026, 3:19 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a2b7b84ec00819086a25d9ff017a6b1 |
completed | June 12, 2026, 3:22 a.m. |
Created at: April 30, 2026, 10:58 p.m.