Triple
T35532448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Mamuju |
E1026837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mandar polity |
C19614
|
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: Mandar polity Context triple: [Kingdom of Mamuju, instanceOf, Mandar polity]
-
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.
Tai polity
A Tai polity is a premodern socio-political entity formed by Tai-speaking peoples, typically organized around a muang (city-state) structure with a hierarchical ruler, tributary relations, and a mandala-style sphere of influence rather than fixed territorial borders.
-
C.
Balinese polity
A Balinese polity is a traditional socio-political entity in Bali characterized by a hierarchical kingship, ritual authority, and complex relationships between royal courts, villages, and religious institutions.
-
D.
Bugis polity
chosen
A Bugis polity is a traditional socio-political entity of the Bugis people of South Sulawesi, typically organized around a kingdom or chiefdom with its own ruler, customary laws, and maritime-oriented economy and alliances.
-
E.
Sangam-age polity
A Sangam-age polity is a socio-political entity of early historic South India characterized by chieftain-led territories, kin-based authority, and networks of warfare, tribute, and trade as reflected in Sangam literature.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.