Triple
T8815861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noordermarkt |
E209774
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Westerstraat |
E341833
|
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: Westerstraat | Statement: [Noordermarkt, near, Westerstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Westerstraat Context triple: [Noordermarkt, near, Westerstraat]
-
A.
Westerstraat
chosen
Westerstraat is a well-known street in Amsterdam’s historic Jordaan district, noted for its traditional architecture, local shops, and lively neighborhood atmosphere.
-
B.
Rijfstraat
Rijfstraat is a key street in Antwerp’s Diamond District, known for its concentration of diamond-related businesses and trade.
-
C.
Damstraat
Damstraat is a central street in Amsterdam’s historic city center, linking Dam Square with the Red Light District and lined with shops, cafés, and tourist-oriented businesses.
-
D.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
-
E.
Spuistraat
Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
- 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_69cfeb0dab088190b842b20f8a7bc7a0 |
completed | April 3, 2026, 4:30 p.m. |
Created at: March 30, 2026, 6:45 p.m.