Triple
T8390875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Assyrian |
E197939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Semitic language variety |
C13674
|
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: Semitic language variety Context triple: [Neo-Assyrian, instanceOf, Semitic language variety]
-
A.
Semitic language
A Semitic language is a member of a family of related languages originating in the Middle East and North Africa, characterized by root-based morphology and including languages such as Arabic, Hebrew, and Amharic.
-
B.
branch of Semitic languages
chosen
A branch of Semitic languages is a subgroup within the Semitic language family comprising closely related languages that share common historical origins, structural features, and vocabulary.
-
C.
Afroasiatic language branch
The Afroasiatic language branch is a major language family originating in the Middle East and North Africa, encompassing diverse languages such as Arabic, Hebrew, Amharic, and Hausa that share common historical and structural features.
-
D.
Afroasiatic-influenced language
An Afroasiatic-influenced language is a language whose phonology, grammar, or vocabulary shows significant impact from one or more Afroasiatic languages due to contact, substrate, or historical development.
-
E.
Semitic-speaking people
Semitic-speaking people are groups whose native languages belong to the Semitic branch of the Afroasiatic language family, historically including communities such as Arabs, Jews, Assyrians, and others 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.