Triple
T8066434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Han |
E188254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Warring States period 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: Warring States period state Context triple: [State of Han, instanceOf, Warring States period state]
-
A.
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.
-
B.
one of the Three Kingdoms of Korea
One of the Three Kingdoms of Korea is a major ancient Korean state—Goguryeo, Baekje, or Silla—that existed between the 1st century BCE and 7th century CE and played a central role in shaping early Korean history, culture, and territorial formation.
-
C.
Jurchen-led state
A Jurchen-led state is a political entity in which the Jurchen people hold primary ruling authority, shaping its governance, military organization, and cultural policies.
-
D.
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.
-
E.
vassal state
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.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:26 p.m.