Triple
T17941068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian–Ottoman frontier |
E448588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern frontier |
C3245
|
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 modern frontier Context triple: [Hungarian–Ottoman frontier, instanceOf, early modern frontier]
-
A.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
B.
early modern polity
chosen
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
-
C.
Frontier War
Frontier War is a prolonged, often low-intensity conflict that occurs along or beyond a political or cultural boundary, characterized by skirmishes, raids, and contested control of sparsely governed territories.
-
D.
early modern city
An early modern city is an urban center from roughly the 15th to 18th centuries characterized by growing commercial activity, evolving political and administrative institutions, dense mixed-use neighborhoods, and emerging social stratification shaped by trade, religion, and state formation.
-
E.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.