Triple
T10359970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Zhou |
E244107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Zhou dynasty politician |
C26241
|
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: Zhou dynasty politician Context triple: [Duke of Zhou, instanceOf, Zhou dynasty politician]
-
A.
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.
-
B.
Zhou dynasty ruler
chosen
A Zhou dynasty ruler is a sovereign who governed territories under the Zhou dynasty in ancient China, exercising political, military, and ritual authority within a hierarchical feudal system.
-
C.
Spring and Autumn period ruler
A Spring and Autumn period ruler is a monarch who governed one of the Chinese states between roughly 770–476 BCE, navigating complex interstate rivalries, ritual authority, and the early development of hegemonic power.
-
D.
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.
-
E.
Warring States period ruler
A Warring States period ruler is a sovereign who governed one of the competing Chinese states between the 5th and 3rd centuries BCE, navigating constant warfare, shifting alliances, and internal reforms to consolidate power and ensure survival.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:59 a.m.