Triple
T5262408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ourthe |
E118855
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Esneux |
E348311
|
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: Esneux | Statement: [Ourthe, flowsThrough, Esneux]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esneux Context triple: [Ourthe, flowsThrough, Esneux]
-
A.
Esneux
chosen
Esneux is a municipality in the province of Liège in Wallonia, Belgium, known for its scenic setting in the Ourthe River valley.
-
B.
Verzenay
Verzenay is a renowned Grand Cru wine-producing village in France’s Champagne region, particularly noted for its Pinot Noir vineyards on the Montagne de Reims.
-
C.
Vaux-sur-Sûre
Vaux-sur-Sûre is a rural municipality in the Luxembourg province of Wallonia in southeastern Belgium, known for its agricultural landscape and proximity to the Sûre River.
-
D.
Seneffe
Seneffe is a municipality in the province of Hainaut in Wallonia, Belgium, historically notable as the site of a major 17th-century battle during the Franco-Dutch War.
-
E.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfb1324c2c8190ba2a1c5708ba88e5 |
completed | March 22, 2026, 9:06 a.m. |
Created at: March 20, 2026, 1:50 p.m.