Triple
T28535589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanigalbat |
E722153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian provincial territory |
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: Assyrian provincial territory Context triple: [Hanigalbat, instanceOf, Assyrian provincial territory]
-
A.
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.
-
B.
Achaemenid province
An Achaemenid province is an administrative region within the Achaemenid Persian Empire, governed by a satrap or local authority responsible for taxation, security, and implementing imperial policies.
-
C.
Sasanian province
A Sasanian province was an administrative territorial unit of the Sasanian Empire, governed by appointed officials responsible for taxation, justice, and military organization within its boundaries.
-
D.
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.
-
E.
Syro-Aramean polity
A Syro-Aramean polity is a historical or conceptual political entity rooted in the cultural, linguistic, and territorial interplay of ancient Syrian and Aramean societies in the Near East.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:31 a.m.