Triple
T22020469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel of Verdun |
E543830
|
entity |
| Predicate | notableBattle |
P259
|
FINISHED |
| Object | Verdun |
—
|
NE NERFINISHED |
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: Verdun | Statement: [Angel of Verdun, notableBattle, Verdun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Verdun Context triple: [Angel of Verdun, notableBattle, Verdun]
-
A.
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.
-
B.
Verdun
Verdun is a tram stop on the Tramway de Tours network in the city of Tours, France.
-
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.
Verdun, France
chosen
Verdun, France is a historic northeastern French city on the Meuse River, best known as the site of one of World War I’s largest and bloodiest battles.
-
E.
de Verdun
De Verdun is a Norman-English noble family name associated with medieval aristocratic lineages in England and Ireland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c6b5fc8190bc49ddb058f28a44 |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:23 p.m.