Triple
T5762226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mint Tower |
E127122
|
entity |
| Predicate | locatedAtIntersectionOf |
P15085
|
FINISHED |
| Object | Vijzelstraat |
E25955
|
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: Vijzelstraat | Statement: [Mint Tower, locatedAtIntersectionOf, Vijzelstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vijzelstraat Context triple: [Mint Tower, locatedAtIntersectionOf, Vijzelstraat]
-
A.
Vijzelstraat
chosen
Vijzelstraat is a major street in central Amsterdam, Netherlands, running between the city’s historic canals and serving as an important traffic and commercial route.
-
B.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
-
C.
Lepelstraat
Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
-
D.
Domstraat
Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
-
E.
Raadhuisstraat
Raadhuisstraat is a central street in Amsterdam, Netherlands, known for connecting Dam Square to the Jordaan district and for its historic architecture and shops.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0293bbf2081908d40d76c4eb863ae |
completed | March 22, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b0c6c3e08190b0118908ecb85df2 |
completed | March 23, 2026, 3:17 a.m. |
Created at: March 22, 2026, 3:49 p.m.