Triple
T9415018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Baerlestraat |
E226996
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | Hobbemastraat |
E712084
|
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: Hobbemastraat | Statement: [Van Baerlestraat, hasJunctionWith, Hobbemastraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hobbemastraat Context triple: [Van Baerlestraat, hasJunctionWith, Hobbemastraat]
-
A.
Hobbemastraat
chosen
Hobbemastraat is a street in Amsterdam, Netherlands, known for its proximity to major museums and cultural attractions near Museumplein.
-
B.
Hoveniersstraat
Hoveniersstraat is a prominent street in Antwerp, Belgium, renowned as a central hub of the city's diamond trade and industry.
-
C.
De Lairessestraat
De Lairessestraat is a prominent street in Amsterdam’s Oud-Zuid district, known for its upscale residential buildings and proximity to cultural attractions.
-
D.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
-
E.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c7bd648190b17f082883c98239 |
completed | April 1, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d11026b8688190b958ca65dae2d588 |
completed | April 4, 2026, 1:20 p.m. |
Created at: March 30, 2026, 7:48 p.m.