Triple
T14901889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mons Prison |
E360025
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | city of Mons |
E415995
|
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 Mons | Statement: [Mons Prison, locatedNear, city of Mons]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Mons Context triple: [Mons Prison, locatedNear, city of Mons]
-
A.
Mons-lez-Liège
Mons-lez-Liège is a village in the province of Liège in Wallonia, Belgium, known today as a district within the municipality of Flémalle.
-
B.
Mons, Belgium
chosen
Mons, Belgium is a historic city in the Wallonia region that serves as a key military and administrative hub, notably hosting major NATO institutions.
-
C.
Braine-le-Comte
Braine-le-Comte is a municipality in the province of Hainaut in Wallonia, Belgium, known for its historic town center and role as a regional transport hub.
-
D.
Namur
Namur is a historic Belgian city and the capital of Wallonia, located at the confluence of the Meuse and Sambre rivers.
-
E.
Mont-Saint-Guibert
Mont-Saint-Guibert is a municipality in the province of Walloon Brabant in the French-speaking Walloon region of Belgium.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60b24008190bd272c0d61329400 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72b30c6881908b80ca96fb5b716f |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:11 a.m.