Triple
T26357028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadramite kingdom |
E663091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient South Arabian kingdom |
C16071
|
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 South Arabian kingdom Context triple: [Hadramite kingdom, instanceOf, ancient South Arabian kingdom]
-
A.
South Arabian kingdom
chosen
A South Arabian kingdom is an ancient political entity that arose in the southern Arabian Peninsula, characterized by complex social structures, trade-based economies, and distinctive cultural and religious practices.
-
B.
Serer kingdom
A Serer kingdom is a precolonial West African polity ruled by Serer monarchs, characterized by complex social hierarchies, indigenous religious institutions, and control over regional trade and agriculture in areas of present-day Senegal, the Gambia, and Mauritania.
-
C.
Berber kingdom
A Berber kingdom is a historically or contemporarily Berber-ruled political entity in North Africa or the Sahara, characterized by Berber language, culture, and social structures as central to its governance and identity.
-
D.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
E.
South Arabian people
South Arabian people are the indigenous populations of the southern Arabian Peninsula, historically including groups such as the Sabaeans, Himyarites, and related communities, known for their ancient kingdoms, trade networks, and distinctive Semitic languages and cultures.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:48 p.m.