Triple
T1415471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Pijp |
E31903
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Pijpbuurt |
E131269
|
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: Pijpbuurt | Statement: [De Pijp, hasAlternativeName, Pijpbuurt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pijpbuurt Context triple: [De Pijp, hasAlternativeName, Pijpbuurt]
-
A.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
B.
De Pijp neighborhood
chosen
De Pijp neighborhood is a vibrant, densely populated district in Amsterdam known for its multicultural atmosphere, lively cafés, and the famous Albert Cuyp Market.
-
C.
Oud-Zuid
Oud-Zuid is an affluent, culturally rich district in Amsterdam known for its museums, upscale shopping streets, and historic architecture.
-
D.
Muntplein
Muntplein is a central square in Amsterdam, known as a busy traffic hub near the historic city center and the Munttoren (Mint Tower).
-
E.
Bloemendaal
Bloemendaal is a coastal municipality in North Holland, Netherlands, known for its beaches, dunes, and affluent residential areas.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c402b1648190b87802d9beb2712e |
completed | March 1, 2026, 10:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad08ae530081909695bde0d9c46d41 |
completed | March 8, 2026, 5:27 a.m. |
Created at: March 1, 2026, 7:59 p.m.