Triple
T20499155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | river Eem |
E503254
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Heiligenbergerbeek |
—
|
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: Heiligenbergerbeek | Statement: [river Eem, hasTributary, Heiligenbergerbeek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heiligenbergerbeek Context triple: [river Eem, hasTributary, Heiligenbergerbeek]
-
A.
Heiligenbergerbeek
chosen
Heiligenbergerbeek is a small stream in the Netherlands that flows through the Randenbroek area of Amersfoort.
-
B.
Lembeekse Beek
Lembeekse Beek is a stream in Belgium that serves as a notable tributary within the Zenne river basin.
-
C.
Prinsenbeek
Prinsenbeek is a village in the Dutch province of North Brabant, now part of the municipality of Breda and known for its suburban character and proximity to the city.
-
D.
Vierlingsbeek
Vierlingsbeek is a village in the Dutch province of North Brabant, known for its rural character and location along the river Maas.
-
E.
Sambeek
Sambeek is a village in the Dutch province of North Brabant, located within the municipality of Boxmeer.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbff210819089900e9a35911f48 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.