Triple
T17824723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyle River |
E445083
|
entity |
| Predicate | hasTownOnRiver |
P26693
|
FINISHED |
| Object | Ottignies |
—
|
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: Ottignies | Statement: [Dyle River, hasTownOnRiver, Ottignies]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ottignies Context triple: [Dyle River, hasTownOnRiver, Ottignies]
-
A.
Ottignies
chosen
Ottignies is a town in central Belgium, in Walloon Brabant, known as a regional transport hub on the rail route between Brussels and Namur.
-
B.
Tubize
Tubize is a municipality in Walloon Brabant, Belgium, known for its industrial heritage and location along the Brussels–Charleroi Canal.
-
C.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
-
D.
Bütgenbach
Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
-
E.
Binche
Binche is a historic town in the Walloon region of Belgium, renowned for its well-preserved medieval architecture and its UNESCO-recognized Carnival of Binche.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4891352ac8190ad3d669fea1c9fbb |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.