Triple
T17052956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borne |
E413746
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Bornsebeek |
—
|
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: Bornsebeek | Statement: [Borne, locatedOn, Bornsebeek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bornsebeek Context triple: [Borne, locatedOn, Bornsebeek]
-
A.
Groesbeek
Groesbeek is a village in the Dutch province of Gelderland, known for its hilly landscape, World War II history, and wine production.
-
B.
Vlezenbeek
Vlezenbeek is a village in the Flemish Brabant province of Belgium, known for its rural character and proximity to Brussels.
-
C.
Boortmeerbeek
Boortmeerbeek is a municipality in the Flemish Brabant province of Belgium, situated between Leuven and Mechelen.
-
D.
Schipbeek
chosen
Schipbeek is a small river in the eastern Netherlands that flows through the provinces of Overijssel and Gelderland before joining the IJssel.
-
E.
Zuunbeek
Zuunbeek is a small stream in Belgium that serves as a right-bank tributary of the River Dender.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa491008190ad013ee37532aa51 |
completed | April 18, 2026, 7:25 p.m. |
Created at: April 10, 2026, 5:34 a.m.