Triple
T7327628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabaean kingdom |
E168914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Arabian civilization |
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: South Arabian civilization Context triple: [Sabaean kingdom, instanceOf, South Arabian civilization]
-
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.
Arabian polity
An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
-
C.
South Arabian language
A South Arabian language is a member of a group of Semitic languages historically spoken in the southern Arabian Peninsula, characterized by distinct phonological, morphological, and script traditions separate from other Arabic varieties.
-
D.
ancient Arabian tribe
An ancient Arabian tribe is a historically rooted kinship-based social group from the Arabian Peninsula, characterized by shared ancestry, territory, customs, and often a distinct dialect or cultural identity.
-
E.
Semitic culture
Semitic culture encompasses the shared linguistic, religious, and social traditions of peoples historically speaking Semitic languages, such as Arabs, Jews, and Assyrians, across the Middle East and surrounding regions.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:03 p.m.