Triple
T2480682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Namur (1692) |
E55806
|
entity |
| Predicate | captured |
P4236
|
FINISHED |
| Object | city of Namur |
E107798
|
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: city of Namur | Statement: [Siege of Namur (1692), captured, city of Namur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Namur Context triple: [Siege of Namur (1692), captured, city of Namur]
-
A.
Namur
chosen
Namur is a historic Belgian city and the capital of Wallonia, located at the confluence of the Meuse and Sambre rivers.
-
B.
Liège
Liège is a major city in eastern Belgium known for its industrial heritage, vibrant cultural scene, and position along the Meuse River.
-
C.
Dendermonde
Dendermonde is a historic city in East Flanders, Belgium, known for its medieval architecture and UNESCO-recognized Ros Beiaard procession.
-
D.
Maubeuge
Maubeuge is a fortified industrial town in northern France near the Belgian border, historically significant for its strategic military position.
-
E.
La Roche-en-Ardenne
La Roche-en-Ardenne is a picturesque town in Belgium’s Ardennes region, known for its medieval castle ruins, outdoor activities, and World War II history.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd160a9708190b28d2f5538ea129a |
completed | March 7, 2026, 7:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af17b146d881909672e9cd4a501a11 |
completed | March 9, 2026, 6:55 p.m. |
Created at: March 6, 2026, 9:45 p.m.