Triple
T32576144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gongsun Hong |
E832649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Han official |
C60083
|
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: Western Han official Context triple: [Gongsun Hong, instanceOf, Western Han official]
-
A.
Eastern Han dynasty official
An Eastern Han dynasty official was a government bureaucrat serving the Chinese empire (25–220 CE), responsible for administering local or central affairs, implementing imperial policies, collecting taxes, and maintaining social order within the Confucian-based administrative hierarchy.
-
B.
Western Han noble
A Western Han noble is a high-ranking aristocrat in the Western Han Dynasty who holds hereditary titles, land, and political influence within the imperial hierarchy.
-
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.
Western Han dynasty emperor
A Western Han dynasty emperor is the supreme hereditary ruler of the Western Han period of China (206 BCE–9 CE), holding ultimate political, military, and ritual authority over the empire.
-
E.
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.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.