Triple

T7078063
Position Surface form Disambiguated ID Type / Status
Subject Yser Front E164870 entity
Predicate alsoKnownAs P39 FINISHED
Object IJzerfront E164870 NE 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: IJzerfront | Statement: [Yser Front, alsoKnownAs, IJzerfront]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IJzerfront
Context triple: [Yser Front, alsoKnownAs, IJzerfront]
  • A. Operation Mars
    Operation Mars was a major Soviet offensive launched in November 1942 against Germany’s Army Group Centre on the Eastern Front during World War II.
  • B. Yser Front chosen
    The Yser Front was a key World War I defensive line in western Belgium where Belgian forces halted the German advance along the Yser River.
  • C. Baltic Front
    The Baltic Front was a major Soviet Red Army formation during World War II that conducted operations in the Baltic region against German forces.
  • D. Haberschlacht
    Haberschlacht is a village in the German state of Baden-Württemberg that forms one of the districts of the wine-growing town of Brackenheim.
  • E. Grenzbrigade Küste
    Grenzbrigade Küste was a coastal border guard formation of East Germany’s Volksmarine responsible for securing and monitoring the maritime frontiers of the German Democratic Republic.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6887cbc6c8190bdfac42d940f4d8a completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4ee29288190a9a3fa7a6c713d8f completed March 27, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7946dbf048190a6307fefeb1dd6a9 completed March 28, 2026, 8:42 a.m.
Created at: March 27, 2026, 2:40 p.m.