Triple

T20964110
Position Surface form Disambiguated ID Type / Status
Subject Siege of Adrianople (1912–1913) E516321 entity
Predicate defender P696 FINISHED
Object Ottoman garrison of Adrianople — 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: Ottoman garrison of Adrianople | Statement: [Siege of Adrianople (1912–1913), defender, Ottoman garrison of Adrianople]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Ottoman garrison of Adrianople
Context triple: [Siege of Adrianople (1912–1913), defender, Ottoman garrison of Adrianople]
  • A. Byzantine garrison of Adrianople
    The Byzantine garrison of Adrianople was the imperial military force stationed in the strategic Thracian city of Adrianople, tasked with defending it against enemy sieges and incursions such as those during the early 9th century.
  • B. Ottoman garrison of Belgrade
    The Ottoman garrison of Belgrade was the fortress city’s defending military force of the Ottoman Empire, tasked with holding this key strategic stronghold on the Danube frontier.
  • C. Byzantine garrison of Thessalonica
    The Byzantine garrison of Thessalonica was the imperial military force stationed in the empire’s second city, tasked with defending it against external threats such as the Norman invasion of 1185.
  • D. Byzantine garrison of Nicomedia
    The Byzantine garrison of Nicomedia was the imperial military force stationed in the strategically important city of Nicomedia, tasked with defending this key stronghold in northwestern Asia Minor.
  • E. Novo-Bayazet
    Novo-Bayazet is a historical town in the South Caucasus region that served as the administrative center of the Novo-Bayazet uezd in the Russian Empire.
  • 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: Ottoman garrison of Adrianople
Target entity description: The Ottoman garrison of Adrianople was the imperial military force stationed in the strategic fortress city of Adrianople (Edirne), tasked with defending it during the First Balkan War.
  • A. Byzantine garrison of Adrianople
    The Byzantine garrison of Adrianople was the imperial military force stationed in the strategic Thracian city of Adrianople, tasked with defending it against enemy sieges and incursions such as those during the early 9th century.
  • B. Ottoman garrison of Belgrade
    The Ottoman garrison of Belgrade was the fortress city’s defending military force of the Ottoman Empire, tasked with holding this key strategic stronghold on the Danube frontier.
  • C. Byzantine garrison of Thessalonica
    The Byzantine garrison of Thessalonica was the imperial military force stationed in the empire’s second city, tasked with defending it against external threats such as the Norman invasion of 1185.
  • D. Byzantine garrison of Nicomedia
    The Byzantine garrison of Nicomedia was the imperial military force stationed in the strategically important city of Nicomedia, tasked with defending this key stronghold in northwestern Asia Minor.
  • E. Novo-Bayazet
    Novo-Bayazet is a historical town in the South Caucasus region that served as the administrative center of the Novo-Bayazet uezd in the Russian Empire.
  • 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_69e0b4fde6c48190af1398e7e734629e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb71d644819087e00933fcc26217 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:32 p.m.