Triple
T284823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punic Wars |
E5865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient war |
C441
|
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: ancient war Context triple: [Punic Wars, instanceOf, ancient war]
-
A.
ancient civilization
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
-
B.
war
chosen
War is a large-scale, organized conflict between groups—typically nations or factions—characterized by sustained violence, strategic objectives, and significant political, social, and human consequences.
-
C.
battles
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
D.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
E.
succession war
A succession war is an armed conflict triggered by competing claims to a throne or leadership position, typically following the death, deposition, or disputed legitimacy of a ruler.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.