Triple

T9900997
Position Surface form Disambiguated ID Type / Status
Subject Ypres 1917 E182281 entity
Predicate hasLocation P40 FINISHED
Object Ypres 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 | Statement: [Ypres 1917, hasLocation, Ypres]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ypres
Context triple: [Ypres 1917, hasLocation, Ypres]
  • 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. Messines Ridge
    Messines Ridge is a strategically important elevated area in Flanders, Belgium, that was the focus of intense fighting during World War I, particularly noted for the massive mine explosions detonated there in 1917.
  • D. 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.
  • E. 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.
  • 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_69ca82876f8081909cf75df0f99bb13f completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cdb4e221448190b536742d1269f9d7 completed April 2, 2026, 12:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eb2125208190b4cf549d67d1ca42 completed April 5, 2026, 4:54 a.m.
Created at: March 30, 2026, 8:40 p.m.