Triple
T1986492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Ypres |
E43152
|
entity |
| Predicate | front |
P1699
|
FINISHED |
| Object | Ypres Salient |
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 Salient | Statement: [Second Battle of Ypres, front, Ypres Salient]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ypres Salient Context triple: [Second Battle of Ypres, front, Ypres Salient]
-
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.
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.
-
C.
Elsenborn Ridge
Elsenborn Ridge is a strategically important high ground in eastern Belgium that played a key defensive role for Allied forces during World War II’s Battle of the Bulge.
-
D.
Somme, France
Somme, France is a department in northern France best known as the site of major World War I battles, including the Battle of the Somme.
-
E.
Battle of Passchendaele
The Battle of Passchendaele was a brutal and muddy First World War offensive in 1917 near Ypres, Belgium, notorious for its massive casualties and minimal territorial gains.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8232d788190938f261fd4b2f2fd |
completed | March 7, 2026, 5:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0ad53ccc8190b0e0f44cfddfe9a4 |
completed | March 8, 2026, 11:48 p.m. |
Created at: March 4, 2026, 7:37 p.m.