Triple

T4120624
Position Surface form Disambiguated ID Type / Status
Subject Ypres E92602 entity
Predicate hasGermanName P1435 FINISHED
Object Ypern 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: Ypern | Statement: [Ypres, hasGermanName, Ypern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ypern
Context triple: [Ypres, hasGermanName, Ypern]
  • 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. Verdun
    Verdun is a borough of Montreal, Quebec, known for its historic waterfront along the St. Lawrence River and its mix of residential neighborhoods and urban amenities.
  • C. Battle of Verdun
    The Battle of Verdun was one of the longest and bloodiest engagements of World War I, symbolizing the brutal attrition warfare on the Western Front between France and Germany in 1916.
  • 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. Vimy Ridge
    Vimy Ridge is a prominent escarpment in northern France that was the site of a major First World War battle, particularly noted for the Canadian Corps’ successful assault in 1917.
  • 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_69aed9685f70819086932777aec8d959 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69af0203b8c88190b08dd64800a37168 completed March 9, 2026, 5:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69b576ae8ef08190ba2adcbd2bbe8d35 completed March 14, 2026, 2:54 p.m.
Created at: March 9, 2026, 3:41 p.m.