Triple
T31881884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samerina |
E813903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian provincial center |
C9491
|
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 center Context triple: [Samerina, instanceOf, Assyrian provincial center]
-
A.
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.
-
B.
Mesopotamian city
chosen
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.
-
C.
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.
-
D.
Phrygian city
A Phrygian city is an ancient urban settlement located in the historical region of Phrygia in central Anatolia, characterized by its distinctive rock-cut architecture, religious monuments, and role in the Phrygian kingdom’s political and cultural life.
-
E.
Sasanian frontier stronghold
A Sasanian frontier stronghold is a fortified military installation positioned along the empire’s borders to control strategic routes, monitor enemy movements, and defend against incursions.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:56 p.m.