Triple

T2988116
Position Surface form Disambiguated ID Type / Status
Subject Royal Berkshire Regiment E80677 entity
Predicate battleHonour P12198 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: [Royal Berkshire Regiment, battleHonour, Ypres]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ypres
Context triple: [Royal Berkshire Regiment, battleHonour, 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. 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.
  • D. 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.
  • E. Vimy, France
    Vimy, France is a commune in northern France best known as the site of the Canadian National Vimy Memorial commemorating World War I.
  • 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_69ad8b16c3488190b47b6aa7a59a335b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99c9cdd081908fa8094a3ac1f8d3 completed March 8, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b108fe2568819083a8f97b37dc8340 completed March 11, 2026, 6:17 a.m.
Created at: March 8, 2026, 2:59 p.m.