Triple
T20218479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henk Sneevlietweg |
E495187
|
entity |
| Predicate | hasNearbyRoad |
P11435
|
FINISHED |
| Object | Henk Sneevlietweg (street) |
—
|
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: Henk Sneevlietweg (street) | Statement: [Henk Sneevlietweg, hasNearbyRoad, Henk Sneevlietweg (street)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henk Sneevlietweg (street) Context triple: [Henk Sneevlietweg, hasNearbyRoad, Henk Sneevlietweg (street)]
-
A.
Henk Sneevlietweg
chosen
Henk Sneevlietweg is a metro station in Amsterdam named after Dutch communist and resistance leader Henk Sneevliet.
-
B.
P.C. Hooftstraat
P.C. Hooftstraat is an upscale shopping street in Amsterdam known for its luxury boutiques and high-end international fashion brands.
-
C.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
-
D.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
E.
Wiertzstraat
Wiertzstraat is a street in Brussels, Belgium, located in the European Quarter near key European Union institutions.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66edaeeb08190bb74bd4a10aceca2 |
completed | April 20, 2026, 6:22 p.m. |
Created at: April 11, 2026, 11:39 p.m.