Triple
T20302838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian railway line 53 |
E505526
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Opwijk |
—
|
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: Opwijk | Statement: [Belgian railway line 53, passesThrough, Opwijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opwijk Context triple: [Belgian railway line 53, passesThrough, Opwijk]
-
A.
Opwijk
chosen
Opwijk is a municipality in the Flemish Brabant province of Belgium, situated in the Dutch-speaking region of Flanders.
-
B.
Zijdelwaard
Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
-
C.
Passewaaij
Passewaaij is a residential neighborhood of the Dutch city of Tiel, located in the province of Gelderland.
-
D.
Wijster
Wijster is a village in the Dutch province of Drenthe, known historically for its rural character and the nearby former waste disposal site that was the scene of a 1975 train hijacking.
-
E.
Noordwyk
Noordwyk is a residential suburb located within the Midrand area of Johannesburg, South Africa.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773e0864819095d272659cd2074d |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:17 a.m.