Triple

T9443519
Position Surface form Disambiguated ID Type / Status
Subject Passchendaele Canadian Memorial E227705 entity
Predicate near P350 FINISHED
Object Ypres (Ieper) E92602 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: Ypres (Ieper) | Statement: [Passchendaele Canadian Memorial, near, Ypres (Ieper)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ypres (Ieper)
Context triple: [Passchendaele Canadian Memorial, near, Ypres (Ieper)]
  • A. Ypres chosen
    Ypres is a historic town in western Belgium that was the site of several major and devastating battles during World War I.
  • B. Armentières
    Armentières is a commune in northern France near the Belgian border, historically known for its textile industry and World War I significance.
  • C. St. Vith
    St. Vith is a town in eastern Belgium that became a strategically important battleground during World War II, particularly noted for its role in the Battle of the Bulge.
  • D. Duinkerke
    Duinkerke is the Dutch name for Dunkirk, a historic port city in northern France known for its pivotal World War II evacuation.
  • E. Yser Front
    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.
  • 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_69ca843884488190ad6cbe0153088234 completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7f3171248190b92ab990371e63f5 completed April 1, 2026, 8:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12cd9ae548190bf985c72196eb0bd completed April 4, 2026, 3:23 p.m.
Created at: March 30, 2026, 7:51 p.m.