Triple
T27764956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German theatre of the Thirty Years' War |
E701575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical region of conflict |
C45840
|
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: historical region of conflict Context triple: [German theatre of the Thirty Years' War, instanceOf, historical region of conflict]
-
A.
history of a region
A history of a region is a structured account of the social, political, economic, and cultural developments that have shaped a specific geographic area over time.
-
B.
early modern conflict zone
chosen
An early modern conflict zone is a geographically and politically contested area between roughly 1500 and 1800 where competing states, empires, or factions engaged in sustained military, economic, and ideological struggles that reshaped local societies and regional power balances.
-
C.
conflict-affected area
A conflict-affected area is a geographic region where ongoing or recent armed violence, political instability, or social unrest significantly disrupts normal life, governance, and access to essential services.
-
D.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
E.
regional rivalry
Regional rivalry is a competitive and often tense relationship between neighboring areas or countries, driven by historical, cultural, economic, or political differences as they vie for influence, resources, or prestige.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:30 p.m.