Triple
T28283982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanlin Academician |
E713229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Hanlin Academy |
C53828
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the Hanlin Academy Context triple: [Hanlin Academician, instanceOf, member of the Hanlin Academy]
-
A.
Yuan dynasty official
A Yuan dynasty official was an appointed administrator or bureaucrat serving under the Mongol-led Yuan Empire (1271–1368), responsible for implementing imperial policies, managing local governance, and overseeing taxation and legal affairs within a hierarchical, often ethnically stratified, governmental system.
-
B.
Tang dynasty official
A Tang dynasty official is a government administrator or bureaucrat serving the Tang Empire, typically selected through the imperial examination system to manage civil, military, and fiscal affairs.
-
C.
member of the Chinese Academy of Sciences
A member of the Chinese Academy of Sciences is a distinguished scientist elected to China’s premier academic institution in recognition of outstanding contributions to scientific research and technological innovation.
-
D.
Song dynasty politician
A Song dynasty politician is an official who served in the governmental and bureaucratic structures of China’s Song dynasty, influencing administration, policy, and state affairs.
-
E.
Yuan dynasty scholar
A Yuan dynasty scholar is an educated intellectual of 13th–14th century China who engaged in classical learning, literary pursuits, and official or private scholarship under Mongol rule.
- F. None of above. chosen
Provenance (1 batch)
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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:25 p.m.