Triple
T15027416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razihi |
E378252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | modern South Arabian-related language |
C12548
|
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: modern South Arabian-related language Context triple: [Razihi, instanceOf, modern South Arabian-related language]
-
A.
South Arabian language
chosen
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.
-
B.
ancient North Arabian dialect
An ancient North Arabian dialect is a historical variety of the North Arabian branch of the Semitic languages, attested in inscriptions and texts from pre-Islamic northern Arabia.
-
C.
Western Desert language
A Western Desert language is a member of a closely related group of Australian Aboriginal languages spoken across the Western Desert region, sharing common linguistic features and cultural heritage.
-
D.
Saharan language
A Saharan language is a member of a small family of related languages spoken primarily in the central Sahara region of Africa, characterized by shared grammatical structures and vocabulary distinct from neighboring language families.
-
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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:58 a.m.