Triple
T17616462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Parushni |
E429095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vedic-era conflict |
C39446
|
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: Vedic-era conflict Context triple: [Battle of the Parushni, instanceOf, Vedic-era 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.
Hellenistic-period conflict
A Hellenistic-period conflict is a military or political struggle occurring between Alexander the Great’s death in 323 BCE and the Roman conquest of the eastern Mediterranean, typically involving successor kingdoms vying for territory, power, and influence.
-
C.
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.
-
D.
7th-century conflict
A 7th-century conflict is a military or political struggle that occurred between 600 and 699 CE, typically involving early medieval states, empires, or tribes and shaped by the religious, cultural, and territorial dynamics of that era.
-
E.
6th-century conflict
A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.