Triple
T19529513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinhan confederacy |
E488621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Korean confederacy |
C8668
|
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 Korean confederacy Context triple: [Jinhan confederacy, instanceOf, ancient Korean confederacy]
-
A.
tribal confederation
chosen
A tribal confederation is a loose alliance of distinct tribes that cooperate for mutual defense, governance, or shared interests while retaining their individual identities and autonomy.
-
B.
Cham polity
Cham polity refers to the historical political entities and state structures formed by the Cham people in mainland Southeast Asia, particularly in what is now central and southern Vietnam, characterized by maritime trade, Hindu-Buddhist cultural influences, and shifting regional power dynamics.
-
C.
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.
-
D.
Jukun traditional state
Jukun traditional state is a historical socio-political entity of the Jukun people in present-day Nigeria, characterized by centralized kingship, ritual authority, and a hierarchical system of governance rooted in indigenous customs and beliefs.
-
E.
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.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:41 p.m.