Triple
T29153734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diyar Rabi'a |
E738980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Upper Mesopotamia |
C25912
|
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: district of Upper Mesopotamia Context triple: [Diyar Rabi'a, instanceOf, district of Upper Mesopotamia]
-
A.
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.
-
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
chosen
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.
Mesopotamian city
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
E.
region of ancient Cilicia
A region of ancient Cilicia is a historically defined geographic area within the larger territory of Cilicia, characterized by its distinct political, cultural, or administrative identity in antiquity.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:43 a.m.