Triple
T26106695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almaqah |
E658555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sabaean deity |
C45000
|
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: Sabaean deity Context triple: [Almaqah, instanceOf, Sabaean deity]
-
A.
pre-Islamic South Arabian deity
chosen
A pre-Islamic South Arabian deity is a divine figure worshiped in ancient South Arabia before the rise of Islam, often associated with local kingdoms, natural forces, or social functions, and venerated through temples, inscriptions, and ritual offerings.
-
B.
ancient North Arabian deity
An ancient North Arabian deity is a divine figure worshiped by pre-Islamic Arabian communities, often associated with local tribes, natural forces, or specific sanctuaries in the northern Arabian Peninsula.
-
C.
Nabataean deity
A Nabataean deity is a divine figure worshiped by the ancient Nabataean people, often associated with specific natural features, trade routes, or aspects of daily life and venerated in temples, shrines, and rock-cut sanctuaries across their territory.
-
D.
ancient Arabian deity
An ancient Arabian deity is a supernatural being worshiped in pre-Islamic Arabia, associated with specific natural forces, tribal identities, or sacred sites, and venerated through rituals, offerings, and local cult practices.
-
E.
pre-Islamic Arabian deity
A pre-Islamic Arabian deity is a supernatural being worshiped in the Arabian Peninsula before the advent of Islam, often associated with natural forces, tribal protection, or specific cultic sites.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:59 p.m.