Triple
T27540879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Jiaodong |
E695231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Han vassal state |
C3295
|
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 vassal state Context triple: [Kingdom of Jiaodong, instanceOf, Western Han vassal state]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
vassal state
chosen
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
E.
Mongol successor state
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:31 p.m.