Triple
T6452706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Wiertz / Wiertzstraat |
E139908
|
entity |
| Predicate | hasDutchName |
P744
|
FINISHED |
| Object |
Wiertzstraat
Wiertzstraat is a street in Brussels, Belgium, located in the European Quarter near key European Union institutions.
|
E598305
|
NE FINISHED |
How this triple was built (4 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: Wiertzstraat | Statement: [Rue Wiertz / Wiertzstraat, hasDutchName, Wiertzstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wiertzstraat Context triple: [Rue Wiertz / Wiertzstraat, hasDutchName, Wiertzstraat]
-
A.
Marnixstraat
Marnixstraat is a major street in central Amsterdam known for its tram lines, bus station, and proximity to popular areas like Leidseplein and the Jordaan.
-
B.
Vijzelstraat
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.
-
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.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Wiertzstraat Triple: [Rue Wiertz / Wiertzstraat, hasDutchName, Wiertzstraat]
Generated description
Wiertzstraat is a street in Brussels, Belgium, located in the European Quarter near key European Union institutions.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Wiertzstraat Target entity description: Wiertzstraat is a street in Brussels, Belgium, located in the European Quarter near key European Union institutions.
-
A.
Marnixstraat
Marnixstraat is a major street in central Amsterdam known for its tram lines, bus station, and proximity to popular areas like Leidseplein and the Jordaan.
-
B.
Vijzelstraat
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.
-
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.
Heemstedestraat
Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
- F. None of above. chosen
Provenance (5 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b62cbc81908b7f1a0dc1ed3e1d |
completed | March 22, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c669de36a08190837817b32074e405 |
completed | March 27, 2026, 11:28 a.m. |
| NEDg | Description generation | batch_69c66bfbdcc881909c68dac942994103 |
completed | March 27, 2026, 11:37 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c66d28430c8190945841d6327e5aef |
completed | March 27, 2026, 11:42 a.m. |
Created at: March 22, 2026, 4:47 p.m.