Triple
T7629036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan Zuid |
E172711
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Apollobuurt |
E498345
|
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: Apollobuurt | Statement: [Plan Zuid, hasPart, Apollobuurt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apollobuurt Context triple: [Plan Zuid, hasPart, Apollobuurt]
-
A.
Apollobuurt
chosen
Apollobuurt is an affluent residential neighborhood in Amsterdam, known for its elegant architecture, broad avenues, and proximity to cultural institutions and green spaces.
-
B.
Dapperbuurt
Dapperbuurt is a lively residential neighborhood in Amsterdam known for its multicultural character and the popular Dappermarkt street market.
-
C.
Willemsparkbuurt
Willemsparkbuurt is a residential neighborhood in Amsterdam, known for its upscale housing, leafy streets, and proximity to Vondelpark and Museumplein.
-
D.
Weesperbuurt
Weesperbuurt is a historic neighborhood in central Amsterdam, known for its canalside streets and proximity to the city’s old Jewish quarter.
-
E.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa84adb08190885138fc9b908ebf |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89ab1132481909e525e90764df041 |
completed | March 29, 2026, 3:21 a.m. |
Created at: March 27, 2026, 3:56 p.m.