Triple

T25993585
Position Surface form Disambiguated ID Type / Status
Subject Bretteville-sur-Laize E646423 entity
Predicate locatedInMilitaryTheater P190027 FINISHED
Object Normandy landings aftermath LITERAL FINISHED

How this triple was built (2 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: Normandy landings aftermath | Statement: [Bretteville-sur-Laize, locatedInMilitaryTheater, Normandy landings aftermath]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInMilitaryTheater
Context triple: [Bretteville-sur-Laize, locatedInMilitaryTheater, Normandy landings aftermath]
  • A. wasFrontlineAreaDuring chosen
    Indicates that a location served as a primary combat or conflict zone during a specified time period.
  • B. hasPrimaryTheatreOfWar
    Indicates that an armed conflict or military operation is chiefly conducted within a particular geographic theatre or region of war.
  • C. basedInDuringConflict
    Indicates that an entity is located or headquartered in a particular place for the duration of a specified conflict or war.
  • D. wartimeLocation
    Indicates the location where an entity is situated or operates during a period of war or armed conflict.
  • E. militaryTheaterCovered
    Indicates that a specified military theater or area of operations falls within the geographic or operational scope covered by another entity (such as a plan, command, or agreement).
  • F. None of above.

Provenance (3 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_69e77e88cb8481908da31d4a00661f55 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: April 22, 2026, 8:57 a.m.