Triple
T19780483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Frontier |
E475116
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Danube Military Frontier |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Danube Military Frontier | Statement: [Military Frontier, hasPart, Danube Military Frontier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Danube Military Frontier Context triple: [Military Frontier, hasPart, Danube Military Frontier]
-
A.
Slavonian Military Frontier
The Slavonian Military Frontier was a borderland district of the Habsburg Monarchy in present-day Croatia, organized as a militarized buffer zone against the Ottoman Empire and populated largely by frontier soldiers and settlers.
-
B.
Transylvanian Military Frontier
The Transylvanian Military Frontier was a militarized border zone of the Habsburg Monarchy in Transylvania, organized for defense against the Ottoman Empire and settled by communities with special military obligations.
-
C.
Banat Military Frontier
The Banat Military Frontier was a borderland district of the Habsburg Monarchy organized as a militarized buffer zone against the Ottoman Empire in the Banat region.
-
D.
Danubian frontier
The Danubian frontier was a key defensive and military boundary of the Roman Empire along the Danube River, guarding its central and eastern European provinces from external threats.
-
E.
Hungarian Banat
Hungarian Banat is the historically Hungarian-inhabited portion of the Banat region in Central Europe, now divided mainly between modern-day Hungary, Romania, and Serbia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Danube Military Frontier Target entity description: The Danube Military Frontier was a borderland military-administrative zone of the Habsburg Monarchy along the Danube River, established as a fortified buffer against Ottoman incursions and settled by militarized communities.
-
A.
Slavonian Military Frontier
The Slavonian Military Frontier was a borderland district of the Habsburg Monarchy in present-day Croatia, organized as a militarized buffer zone against the Ottoman Empire and populated largely by frontier soldiers and settlers.
-
B.
Transylvanian Military Frontier
The Transylvanian Military Frontier was a militarized border zone of the Habsburg Monarchy in Transylvania, organized for defense against the Ottoman Empire and settled by communities with special military obligations.
-
C.
Banat Military Frontier
The Banat Military Frontier was a borderland district of the Habsburg Monarchy organized as a militarized buffer zone against the Ottoman Empire in the Banat region.
-
D.
Danubian frontier
The Danubian frontier was a key defensive and military boundary of the Roman Empire along the Danube River, guarding its central and eastern European provinces from external threats.
-
E.
Hungarian Banat
Hungarian Banat is the historically Hungarian-inhabited portion of the Banat region in Central Europe, now divided mainly between modern-day Hungary, Romania, and Serbia.
- F. None of above. chosen
Provenance (2 batches)
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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65382ff308190832800dd60675f7a |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.