Triple
T18543193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wijhe railway station |
E453153
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Wijhe |
—
|
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: Wijhe | Statement: [Wijhe railway station, locatedIn, Wijhe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wijhe Context triple: [Wijhe railway station, locatedIn, Wijhe]
-
A.
Wijhe
chosen
Wijhe is a village in the Dutch province of Overijssel, known as a historic settlement along the river IJssel.
-
B.
Heijen
Heijen is a village in the Dutch province of Limburg, located in the southeastern Netherlands near the Meuse River.
-
C.
Zijdelwaard
Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
-
D.
Passewaaij
Passewaaij is a residential neighborhood of the Dutch city of Tiel, located in the province of Gelderland.
-
E.
Westerwijtwerd
Westerwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its historic rural character and traditional Dutch countryside setting.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b935c48190a34b17eeae4fd583 |
completed | April 19, 2026, 8:02 p.m. |
Created at: April 10, 2026, 11:38 a.m.