Triple
T28945102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teishebaini |
E730557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Urartian city |
C24271
|
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: Urartian city Context triple: [Teishebaini, instanceOf, Urartian city]
-
A.
Urartian archaeological site
chosen
An Urartian archaeological site is a location containing the material remains—such as fortresses, temples, settlements, and artifacts—of the Iron Age kingdom of Urartu, offering evidence of its political, economic, and religious life.
-
B.
Hittite city
A Hittite city is an urban settlement within the Hittite civilization characterized by fortified architecture, administrative and religious centers, and integration into the political and economic network of the Hittite state.
-
C.
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.
-
D.
Lycian city
A Lycian city is an ancient urban settlement located in the historical region of Lycia in southwestern Anatolia, characterized by its distinctive rock-cut tombs, fortified acropoleis, and integration of Greek, Persian, and indigenous Lycian cultural elements.
-
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.
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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:39 a.m.