Triple
T28065743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wang Anshi |
E709244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Song dynasty politician |
C53735
|
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: Song dynasty politician Context triple: [Wang Anshi, instanceOf, Song dynasty politician]
-
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.
Qin dynasty politician
A Qin dynasty politician was an official or statesman who served in the central or regional administration of the Qin state or empire (221–206 BCE), helping implement its legalist policies, bureaucratic reforms, and imperial governance.
-
D.
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.
-
E.
Song dynasty painter
A Song dynasty painter is an artist active during China’s Song dynasty (960–1279) known for refined brushwork, subtle ink washes, and often poetic, nature-focused compositions that blend painting, calligraphy, and scholarly ideals.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:42 p.m.