Triple
T20691025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burebasaga Confederacy |
E508549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fijian chiefly 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: Fijian chiefly confederacy Context triple: [Burebasaga Confederacy, instanceOf, Fijian chiefly confederacy]
-
A.
Moro polity
Moro polity refers to the traditional and historical systems of governance, authority, and social organization among the Muslim ethnolinguistic groups in the southern Philippines, particularly in Mindanao and the Sulu Archipelago.
-
B.
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.
-
C.
Tongan monarchy
The Tongan monarchy is a hereditary constitutional monarchy that serves as the central traditional and political authority in the Kingdom of Tonga, blending indigenous customs with modern state governance.
-
D.
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.
-
E.
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.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:08 p.m.