Triple
T12129187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht |
E288888
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object | Oudegracht |
E53797
|
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: Oudegracht | Statement: [Utrecht, traversedBy, Oudegracht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oudegracht Context triple: [Utrecht, traversedBy, Oudegracht]
-
A.
Oude Gracht
chosen
Oude Gracht is a historic canal running through the center of Utrecht, Netherlands, known for its unique wharf cellars, waterside terraces, and medieval charm.
-
B.
Amstelkanaal
Amstelkanaal is a canal in Amsterdam that connects the Amstel River with other waterways as part of the city’s historic canal network.
-
C.
Leidsegracht
Leidsegracht is a historic canal in Amsterdam’s canal belt, known for its picturesque bridges and traditional Dutch canal houses.
-
D.
Prinsengracht canal
The Prinsengracht canal is one of Amsterdam’s main historic canals, renowned for its picturesque houseboats, waterside houses, and central role in the city’s canal belt.
-
E.
Bloemgracht
Bloemgracht is a picturesque canal in Amsterdam’s Jordaan district, known for its historic houses and charming, village-like atmosphere.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9158a2c2c8190aaff9d0cce177565 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62a7fd708819090af422a60a69859 |
completed | May 2, 2026, 4:46 p.m. |
Created at: April 8, 2026, 9:49 p.m.