Triple
T33490721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singara |
E857730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasanian frontier stronghold |
C58277
|
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: Sasanian frontier stronghold Context triple: [Singara, instanceOf, Sasanian frontier stronghold]
-
A.
Sasanian palace
A Sasanian palace is a grand royal complex from the Sasanian Empire, characterized by monumental vaulted halls, domed audience chambers, rich stucco and brick decoration, and a layout designed to express imperial power and ceremonial hierarchy.
-
B.
Khazar stronghold
A Khazar stronghold is a fortified military and administrative center of the Khazar Khaganate, typically featuring defensive walls, garrisons, and facilities for governance and trade control.
-
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.
Scythian political center
A Scythian political center is a primary settlement or hub where Scythian elites concentrated their authority, coordinated tribal governance, managed long-distance trade, and conducted key ritual and diplomatic activities.
-
E.
Sogdian city
A Sogdian city is an urban settlement in ancient Sogdiana that functioned as a commercial, cultural, and administrative hub along Central Asian trade routes, particularly the Silk Road.
- F. None of above. chosen
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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.