Triple
T17824718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyle River |
E445083
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object |
Dijlebeek
Dijlebeek is a small stream in Belgium that serves as one of the tributaries feeding into the Dyle River.
|
E1295533
|
NE FINISHED |
How this triple was built (4 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: Dijlebeek | Statement: [Dyle River, hasTributary, Dijlebeek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dijlebeek Context triple: [Dyle River, hasTributary, Dijlebeek]
-
A.
Bierbeek
Bierbeek is a municipality in the Flemish Brabant province of Belgium, located near the city of Leuven.
-
B.
Vlezenbeek
Vlezenbeek is a village in the Flemish Brabant province of Belgium, known for its rural character and proximity to Brussels.
-
C.
Schipbeek
Schipbeek is a small river in the eastern Netherlands that flows through the provinces of Overijssel and Gelderland before joining the IJssel.
-
D.
Boortmeerbeek
Boortmeerbeek is a municipality in the Flemish Brabant province of Belgium, situated between Leuven and Mechelen.
-
E.
Linkebeek
Linkebeek is a small Flemish municipality in the Belgian province of Flemish Brabant, located just south of Brussels.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Dijlebeek Triple: [Dyle River, hasTributary, Dijlebeek]
Generated description
Dijlebeek is a small stream in Belgium that serves as one of the tributaries feeding into the Dyle River.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Dijlebeek Target entity description: Dijlebeek is a small stream in Belgium that serves as one of the tributaries feeding into the Dyle River.
-
A.
Bierbeek
Bierbeek is a municipality in the Flemish Brabant province of Belgium, located near the city of Leuven.
-
B.
Vlezenbeek
Vlezenbeek is a village in the Flemish Brabant province of Belgium, known for its rural character and proximity to Brussels.
-
C.
Schipbeek
Schipbeek is a small river in the eastern Netherlands that flows through the provinces of Overijssel and Gelderland before joining the IJssel.
-
D.
Boortmeerbeek
Boortmeerbeek is a municipality in the Flemish Brabant province of Belgium, situated between Leuven and Mechelen.
-
E.
Linkebeek
Linkebeek is a small Flemish municipality in the Belgian province of Flemish Brabant, located just south of Brussels.
- F. None of above. chosen
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a031b18f3308190a847d0922c090fdb |
completed | May 12, 2026, 12:20 p.m. |
| NEDg | Description generation | batch_6a031c3658988190b59fa17d616cad9b |
completed | May 12, 2026, 12:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a031c9914dc819099da3b2174a5fbc7 |
completed | May 12, 2026, 12:27 p.m. |
Created at: April 10, 2026, 10:15 a.m.