Triple
T28497100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kültepe I (Nakhchivan) |
E721135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Early Bronze Age settlement |
C54136
|
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: Early Bronze Age settlement Context triple: [Kültepe I (Nakhchivan), instanceOf, Early Bronze Age settlement]
-
A.
Late Bronze Age settlement
A Late Bronze Age settlement is a community site from roughly 1550–1200 BCE characterized by domestic structures, storage and craft areas, and material culture reflecting advanced metallurgy, trade networks, and complex social organization.
-
B.
Chalcolithic settlement
A Chalcolithic settlement is a prehistoric community site from the Copper Age characterized by early metal use alongside stone tools, permanent dwellings, and emerging social and economic complexity.
-
C.
Bronze Age period
The Bronze Age period is a historical era characterized by the widespread use of bronze for tools and weapons, the rise of early urban civilizations, and significant advances in trade, writing, and social complexity.
-
D.
Iron Age site
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.
Iron Age territory
An Iron Age territory is a geographically defined area controlled by a community or polity during the Iron Age, characterized by shared cultural practices, political organization, and economic activities.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:04 a.m.