Triple
T6557396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenne |
E152483
|
entity |
| Predicate | hasMajorTributary |
P415
|
FINISHED |
| Object |
Lembeekse Beek
Lembeekse Beek is a stream in Belgium that serves as a notable tributary within the Zenne river basin.
|
E600218
|
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: Lembeekse Beek | Statement: [Zenne, hasMajorTributary, Lembeekse Beek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lembeekse Beek Context triple: [Zenne, hasMajorTributary, Lembeekse Beek]
-
A.
Vierlingsbeek
Vierlingsbeek is a village in the Dutch province of North Brabant, known for its rural character and location along the river Maas.
-
B.
Stevensbeek
Stevensbeek is a small village in the Dutch province of North Brabant, known for its rural character and tranquil surroundings.
-
C.
Dijle
The Dijle is a river in central Belgium that flows through cities such as Leuven and Mechelen before joining other waterways that ultimately form part of the Rhine–Meuse river system.
-
D.
Everbeek
Everbeek is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural landscape and wooded surroundings.
-
E.
River Beult
River Beult is a lowland river in Kent, England, known for its meandering course through rural farmland before joining the River Medway.
- 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: Lembeekse Beek Triple: [Zenne, hasMajorTributary, Lembeekse Beek]
Generated description
Lembeekse Beek is a stream in Belgium that serves as a notable tributary within the Zenne river basin.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lembeekse Beek Target entity description: Lembeekse Beek is a stream in Belgium that serves as a notable tributary within the Zenne river basin.
-
A.
Vierlingsbeek
Vierlingsbeek is a village in the Dutch province of North Brabant, known for its rural character and location along the river Maas.
-
B.
Stevensbeek
Stevensbeek is a small village in the Dutch province of North Brabant, known for its rural character and tranquil surroundings.
-
C.
Dijle
The Dijle is a river in central Belgium that flows through cities such as Leuven and Mechelen before joining other waterways that ultimately form part of the Rhine–Meuse river system.
-
D.
Everbeek
Everbeek is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural landscape and wooded surroundings.
-
E.
River Beult
River Beult is a lowland river in Kent, England, known for its meandering course through rural farmland before joining the River Medway.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae1eb0888190a67b850ac2bca79c |
completed | March 27, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cb862e308190af1028c76484a1ea |
completed | March 27, 2026, 6:25 p.m. |
| NEDg | Description generation | batch_69c6cd05c54c81908bb612e7976bd10a |
completed | March 27, 2026, 6:31 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c6cdc3ea7c8190b63e9a19721fea80 |
completed | March 27, 2026, 6:34 p.m. |
Created at: March 27, 2026, 1:52 p.m.