Triple
T1625083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Chu |
E35122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Chinese state |
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: ancient Chinese state Context triple: [State of Chu, instanceOf, ancient Chinese state]
-
A.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
B.
ancient empire
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.
-
C.
historical province of Japan
A historical province of Japan is a former administrative and geographic division that existed before the modern prefecture system, often retaining cultural and historical significance in regional identity.
-
D.
medieval East Slavic state
A medieval East Slavic state is a historically situated political entity formed by East Slavic peoples between the 9th and 15th centuries, characterized by princely rule, Orthodox Christianity, and a feudal socio-economic structure.
-
E.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.