Triple

T17740101
Position Surface form Disambiguated ID Type / Status
Subject Transylvanian Military Frontier E442829 entity
Predicate similarTo P4460 FINISHED
Object Slavonian 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: Slavonian Military Frontier | Statement: [Transylvanian Military Frontier, similarTo, Slavonian Military Frontier]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Slavonian Military Frontier
Context triple: [Transylvanian Military Frontier, similarTo, Slavonian Military Frontier]
  • A. 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.
  • B. 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.
  • C. Serbian Banat
    Serbian Banat is the northeastern region of Serbia, forming part of the historical Banat area and known for its flat Pannonian landscape, multicultural population, and agricultural significance.
  • D. 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.
  • E. Drina Banovina
    Drina Banovina was an administrative province of the Kingdom of Yugoslavia, named after the Drina River and encompassing parts of present-day Bosnia and Herzegovina 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: Slavonian Military Frontier
Target entity description: 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.
  • A. 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.
  • B. 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.
  • C. Serbian Banat
    Serbian Banat is the northeastern region of Serbia, forming part of the historical Banat area and known for its flat Pannonian landscape, multicultural population, and agricultural significance.
  • D. 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.
  • E. Drina Banovina
    Drina Banovina was an administrative province of the Kingdom of Yugoslavia, named after the Drina River and encompassing parts of present-day Bosnia and Herzegovina 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e47acc2610819099451b02bb51891f completed April 19, 2026, 6:48 a.m.
Created at: April 10, 2026, 10:09 a.m.