Triple
T10537545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam-Zuidoost |
E248610
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bullewijk |
E63536
|
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: Bullewijk | Statement: [Amsterdam-Zuidoost, contains, Bullewijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bullewijk Context triple: [Amsterdam-Zuidoost, contains, Bullewijk]
-
A.
Bullewijk
chosen
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
B.
Westwijk
Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
-
C.
Bloemendaal
Bloemendaal is a coastal municipality in North Holland, Netherlands, known for its beaches, dunes, and affluent residential areas.
-
D.
Bezuidenhout
Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
-
E.
Nieuwendijk
Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a56133c819088285522e64831f7 |
completed | April 7, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65e9136bc8190b35685376da7007e |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 6, 2026, 12:31 p.m.