Triple
T6295873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leidseplein |
E141129
|
entity |
| Predicate | hasNearbyCanal |
P49291
|
FINISHED |
| Object | Leidsegracht |
E24382
|
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: Leidsegracht | Statement: [Leidseplein, hasNearbyCanal, Leidsegracht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leidsegracht Context triple: [Leidseplein, hasNearbyCanal, Leidsegracht]
-
A.
Leidsegracht
chosen
Leidsegracht is a historic canal in Amsterdam’s canal belt, known for its picturesque bridges and traditional Dutch canal houses.
-
B.
Bloemgracht
Bloemgracht is a picturesque canal in Amsterdam’s Jordaan district, known for its historic houses and charming, village-like atmosphere.
-
C.
Westlandgracht
Westlandgracht is a canal in Amsterdam, Netherlands, forming part of the city’s western waterway network.
-
D.
Brouwersgracht
Brouwersgracht is a picturesque historic canal in Amsterdam, renowned for its traditional canal houses, bridges, and central location in the city’s canal belt.
-
E.
Lijnbaansgracht
Lijnbaansgracht is a historic canal in Amsterdam that runs along the edge of the Jordaan neighborhood and forms part of the city’s characteristic canal belt.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0643ac2b48190b2db036ce709e7ea |
completed | March 22, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e41fb4708190b6b1433e27c9276e |
completed | March 27, 2026, 1:57 a.m. |
Created at: March 22, 2026, 4:27 p.m.