Triple
T23243894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire of China |
E581531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese empire |
C4987
|
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: Chinese empire Context triple: [Empire of China, instanceOf, Chinese empire]
-
A.
Eurasian empire
A Eurasian empire is a vast, centralized political entity that spans significant territories across both Europe and Asia, integrating diverse cultures, economies, and governance systems under a single imperial authority.
-
B.
ancient Chinese state
An ancient Chinese state is a historically documented political entity that existed within the territory of what is now China, characterized by its own ruling house, administrative system, culture, and military, and interacting with neighboring states through warfare, diplomacy, and trade.
-
C.
ancient empire
chosen
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
D.
Chinese imperial policy
Chinese imperial policy refers to the evolving set of centralized governance strategies, legal codes, bureaucratic institutions, and ideological doctrines—especially Confucianism—used by successive dynasties to maintain authority, manage society, and regulate relations with neighboring states.
-
E.
emperor of China
The emperor of China was the supreme hereditary ruler of imperial China, regarded as the Son of Heaven and the ultimate political, military, and ritual authority over the Chinese empire.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:10 p.m.