Triple
T29969757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fang Xuanling |
E761284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tang dynasty politician |
C27372
|
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: Tang dynasty politician Context triple: [Fang Xuanling, instanceOf, Tang dynasty politician]
-
A.
Tang dynasty official
chosen
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.
-
B.
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.
-
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.
Tang dynasty poet
A Tang dynasty poet is a literary figure from China’s Tang dynasty (618–907 CE) who composes refined, often lyrical verse that reflects the era’s cultural, philosophical, and aesthetic ideals.
-
E.
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.
- F. None of above.
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:31 p.m.