Triple
T21261078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waalwijk |
E524002
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Heusden |
—
|
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: Heusden | Statement: [Waalwijk, borderedBy, Heusden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heusden Context triple: [Waalwijk, borderedBy, Heusden]
-
A.
Heusden
chosen
Heusden is a historic fortified town in the southern Netherlands known for its well-preserved ramparts and picturesque old harbor.
-
B.
Heusden (Asten)
Heusden (Asten) is a small village in the Dutch province of North Brabant, forming part of the municipality of Asten.
-
C.
Bezuidenhout
Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
-
D.
Deurne
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
E.
Deurne
Deurne is a municipality in the Dutch province of North Brabant, known for its rural character and historic peat extraction areas.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e6a0448190ad412a8fcbbd8ff0 |
completed | April 21, 2026, 8:31 a.m. |
Created at: April 16, 2026, 3:59 p.m.