Triple
T12765388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdamse Bos |
E305108
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Amstelveenseweg |
E497545
|
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: Amstelveenseweg | Statement: [Amsterdamse Bos, borderedBy, Amstelveenseweg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amstelveenseweg Context triple: [Amsterdamse Bos, borderedBy, Amstelveenseweg]
-
A.
Amstelveenseweg
chosen
Amstelveenseweg is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
B.
Scheveningseweg
Scheveningseweg is a major historic road in The Hague, Netherlands, connecting the city center with the seaside district of Scheveningen.
-
C.
Turnhoutsebaan
Turnhoutsebaan is a major thoroughfare and commercial street running through the Antwerp district of Borgerhout in Belgium.
-
D.
Nieuwe Amstelstraat
Nieuwe Amstelstraat is a street in central Amsterdam known for housing the Jewish Historical Museum and other culturally significant buildings.
-
E.
Koninginneweg
Koninginneweg is a notable street in Amsterdam’s Oud-Zuid district, known for its upscale residential buildings and proximity to Vondelpark.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df1ef148190af525532fcb0933b |
completed | April 10, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c0dd657c8190b69e8bf187034360 |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 9, 2026, 5:28 p.m.