Triple
T33924329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazyryk burial ground |
E869706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scythian archaeological site |
C25917
|
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: Scythian archaeological site Context triple: [Pazyryk burial ground, instanceOf, Scythian archaeological site]
-
A.
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.
-
B.
Urartian archaeological site
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.
-
C.
Kura–Araxes culture site
A Kura–Araxes culture site is an archaeological location associated with the Early Bronze Age Kura–Araxes cultural horizon, characterized by its distinctive pottery, architecture, and material remains across the South Caucasus and adjacent regions.
-
D.
Iron Age site
chosen
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
E.
megalithic site
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.