Triple
T31941388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taíno chiefdoms of central Puerto Rico |
E815529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Taíno polities |
C47517
|
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: Taíno polities Context triple: [Taíno chiefdoms of central Puerto Rico, instanceOf, Taíno polities]
-
A.
pre-Columbian polity
chosen
A pre-Columbian polity is a socially and politically organized group or state that existed in the Americas before European contact, characterized by its own systems of governance, economy, and culture.
-
B.
Inca polity
The Inca polity was a highly centralized, hierarchical imperial state in the Andes that integrated diverse ethnic groups through a complex system of administration, tribute, and state-sponsored religion centered on the Sapa Inca.
-
C.
ancient Hawaiian polity
An ancient Hawaiian polity was a hierarchical, territorially defined chiefdom governed by aliʻi (chiefs) and structured around complex social, religious, and land-tenure systems across the Hawaiian Islands.
-
D.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
-
E.
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.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:06 a.m.