Triple
T38224949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimmerian invasion |
E1012116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age conflict |
C62034
|
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: Iron Age conflict Context triple: [Cimmerian invasion, instanceOf, Iron Age conflict]
-
A.
Bronze Age battle
A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
-
B.
Vedic-era conflict
Vedic-era conflict refers to the wars, rivalries, and ritualized battles among early Indo-Aryan tribes and neighboring groups in ancient South Asia, as depicted in Vedic texts, which shaped social hierarchies, territorial control, and religious practices.
-
C.
8th-century BCE conflict
chosen
An 8th-century BCE conflict is a historically documented or inferred military, political, or social struggle that occurred between 800 and 701 BCE, involving states, tribes, or communities of that era.
-
D.
1st-century BCE conflict
A 1st-century BCE conflict is a historically documented military or political struggle that occurred between 100 BCE and 1 BCE, involving organized groups or states engaged in warfare or sustained hostilities.
-
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.
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.