Triple
T26530516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yizhou (Shu territory) |
E670808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territory of Shu Han |
C11189
|
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: territory of Shu Han Context triple: [Yizhou (Shu territory), instanceOf, territory of Shu Han]
-
A.
successor state of the Eastern Han dynasty
The successor state of the Eastern Han dynasty refers to the political entities, most notably the Cao Wei regime, that emerged to claim legitimacy and authority following the collapse of the Eastern Han in 220 CE.
-
B.
mainland territory
Mainland territory is a continuous expanse of land that forms the principal part of a country or region, excluding its islands and overseas possessions.
-
C.
autonomous region of China
An autonomous region of China is a first-level administrative division granted a degree of self-governance and cultural autonomy, typically in areas with significant ethnic minority populations.
-
D.
Han dynasty commandery
A Han dynasty commandery was an administrative division governed by a centrally appointed commandery governor, responsible for civil administration, tax collection, and local security within a defined territorial region of the Han Empire.
-
E.
ancient Chinese state
chosen
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.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:35 a.m.