Triple
T15644641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 監察院 |
E376147
|
entity |
| Predicate | EnglishName |
P3437
|
FINISHED |
| Object | Control Yuan |
E77111
|
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: Control Yuan | Statement: [監察院, EnglishName, Control Yuan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Control Yuan Context triple: [監察院, EnglishName, Control Yuan]
-
A.
Control Yuan
chosen
The Control Yuan is one of the five branches of government in the Republic of China (Taiwan), responsible for oversight, auditing, and impeachment of public officials.
-
B.
Zongzhang
Zongzhang was a brief Chinese imperial era name used during the reign of Emperor Gaozong of the Tang dynasty.
-
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.
Consort Yuan
Consort Yuan was an imperial consort of the late Ming dynasty and wife of the Chongzhen Emperor, associated with the dynasty’s final years before its collapse.
-
E.
Zhidong
Zhidong is the given name of Zhang Zhidong, a prominent late Qing dynasty Chinese official and reformer.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed400ec8190a14a9f7cf3092865 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6790f2288190add8ab0bc0f114bf |
completed | May 9, 2026, 4:57 p.m. |
Created at: April 10, 2026, 4:15 a.m.