Triple

T22601868
Position Surface form Disambiguated ID Type / Status
Subject Siege of Landrecies (1794) E574843 entity
Predicate opponent P437 FINISHED
Object French garrison of Landrecies 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: French garrison of Landrecies | Statement: [Siege of Landrecies (1794), opponent, French garrison of Landrecies]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: French garrison of Landrecies
Context triple: [Siege of Landrecies (1794), opponent, French garrison of Landrecies]
  • A. French garrison of Compiègne
    The French garrison of Compiègne was the royal military force stationed in the fortified town of Compiègne that resisted Burgundian and English forces during the later stages of the Hundred Years’ War.
  • B. French garrison of Huningue
    The French garrison of Huningue was the military force of Napoleonic France stationed at the fortified border town of Huningue, tasked with defending it during late Revolutionary and Napoleonic conflicts.
  • C. French royal garrison of Boulogne
    The French royal garrison of Boulogne was the crown’s military force stationed in the fortified port town of Boulogne, responsible for defending this strategic Channel stronghold during conflicts such as the mid-16th-century wars with England.
  • D. Fort at Étaples
    The Fort at Étaples is a late Roman coastal defensive fortification in northern France that formed part of the Saxon Shore system guarding the English Channel.
  • E. Montmirail
    Montmirail is a historic French locality known for its medieval seigneurial ties, including its association with the powerful noble Enguerrand III, Lord of Coucy.
  • 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: French garrison of Landrecies
Target entity description: The French garrison of Landrecies was the Revolutionary-era military force defending the fortified town of Landrecies against Coalition armies during the War of the First Coalition.
  • A. French garrison of Compiègne
    The French garrison of Compiègne was the royal military force stationed in the fortified town of Compiègne that resisted Burgundian and English forces during the later stages of the Hundred Years’ War.
  • B. French garrison of Huningue
    The French garrison of Huningue was the military force of Napoleonic France stationed at the fortified border town of Huningue, tasked with defending it during late Revolutionary and Napoleonic conflicts.
  • C. French royal garrison of Boulogne
    The French royal garrison of Boulogne was the crown’s military force stationed in the fortified port town of Boulogne, responsible for defending this strategic Channel stronghold during conflicts such as the mid-16th-century wars with England.
  • D. Fort at Étaples
    The Fort at Étaples is a late Roman coastal defensive fortification in northern France that formed part of the Saxon Shore system guarding the English Channel.
  • E. Montmirail
    Montmirail is a historic French locality known for its medieval seigneurial ties, including its association with the powerful noble Enguerrand III, Lord of Coucy.
  • 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_69e245bc11308190b69d794d5d1e0bb6 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1626db69481908ec9f9c7d320d3cb completed April 29, 2026, 1:44 a.m.
Created at: April 17, 2026, 2:50 p.m.