Triple
T11012881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amersfoort |
E260285
|
entity |
| Predicate | railwayStation |
P918
|
FINISHED |
| Object | Amersfoort Vathorst |
E924000
|
NE FINISHED |
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: Amersfoort Vathorst | Statement: [Amersfoort, railwayStation, Amersfoort Vathorst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amersfoort Vathorst Context triple: [Amersfoort, railwayStation, Amersfoort Vathorst]
-
A.
Amersfoort
Amersfoort is a historic city in the province of Utrecht in the Netherlands, known for its well-preserved medieval center and strategic location as a rail and road hub.
-
B.
Amersfoort Schothorst
chosen
Amersfoort Schothorst is a suburban railway station in the Dutch city of Amersfoort that serves as a regional commuter hub.
-
C.
Rijkevoort
Rijkevoort is a village in the Dutch province of North Brabant, known for its rural character and location near the German border.
-
D.
Valkenswaard
Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
-
E.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7978b1e888190b297f107f6021b59 |
completed | April 9, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e890bb9c81908c316a6423e650e6 |
completed | April 20, 2026, 8:49 a.m. |
Created at: April 8, 2026, 9:25 p.m.