Triple
T26045902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Egyptian Satrapy |
E647832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian province |
C26239
|
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: Persian province Context triple: [Second Egyptian Satrapy, instanceOf, Persian province]
-
A.
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.
-
B.
Achaemenid province
chosen
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.
province of Iran
A province of Iran is a primary administrative division of the country, governed by a centrally appointed governor and encompassing multiple counties, cities, and rural districts.
-
D.
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.
-
E.
region of Iran
A region of Iran is a geographically and culturally distinct area within the country, often defined by shared historical, ethnic, linguistic, economic, or environmental characteristics.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:10 a.m.