Triple
T8815860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noordermarkt |
E209774
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Lindengracht |
E279037
|
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: Lindengracht | Statement: [Noordermarkt, near, Lindengracht]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lindengracht Context triple: [Noordermarkt, near, Lindengracht]
-
A.
Lindengracht
chosen
Lindengracht is a historic canal and street in Amsterdam’s Jordaan district, known for its traditional architecture and lively local markets.
-
B.
Singelgracht
Singelgracht is a historic canal forming part of the outer ring of waterways around Amsterdam’s city center.
-
C.
Reguliersgracht
Reguliersgracht is a picturesque canal in Amsterdam’s historic center, renowned for its classic canal houses and iconic series of arched bridges.
-
D.
Elandsgracht
Elandsgracht is a notable street in Amsterdam’s Jordaan neighborhood, known for its local shops, cafes, and historic atmosphere.
-
E.
Prinsengracht
Prinsengracht is one of Amsterdam’s main historic canals, known for its picturesque waterways, houseboats, and traditional canal houses.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdb7d89f081908a98c8b0be4f8910 |
completed | April 3, 2026, 3:23 p.m. |
Created at: March 30, 2026, 6:45 p.m.