Triple
T7378843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Battle of Ypres |
E170195
|
entity |
| Predicate | locatedIn |
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: [First Battle of Ypres, locatedIn, Ypres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ypres Context triple: [First Battle of Ypres, locatedIn, 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
Vimy is a Canadian federal electoral district located in the city of Laval, Quebec, represented in the House of Commons.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c4ad0081909386fbef9f61ae4c |
completed | March 27, 2026, 9:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802d57ae88190840442621d8bef35 |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:08 p.m.