Triple
T33747751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nochiya area |
E864744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian-inhabited region |
C60349
|
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: Assyrian-inhabited region Context triple: [Nochiya area, instanceOf, Assyrian-inhabited region]
-
A.
Assyrian-inhabited region
chosen
An Assyrian-inhabited region is a geographic area where Assyrian people form a significant portion of the population, maintaining their distinct language, culture, and historical presence.
-
B.
region of ancient Syria
A region of ancient Syria is a geographically and culturally defined area within the historical territory known as Syria, characterized by its own cities, trade routes, political entities, and interactions with neighboring civilizations in the ancient Near East.
-
C.
Assyrian province
An Assyrian province is an administrative territorial unit of the ancient Assyrian Empire, governed by an appointed official responsible for taxation, military conscription, and local order under the authority of the Assyrian king.
-
D.
region of ancient Mesopotamia
A region of ancient Mesopotamia is a geographically defined area within the broader Mesopotamian landscape, characterized by shared political, cultural, and economic features during a specific historical period.
-
E.
Assyrian Christian town
An Assyrian Christian town is a settlement predominantly inhabited by Assyrian Christians, characterized by their Syriac language, churches, and cultural traditions rooted in ancient Mesopotamian and early Christian heritage.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.