Triple
T23380718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Wiertz |
E593736
|
entity |
| Predicate | hasNameInDutch |
P13254
|
FINISHED |
| Object | Wiertzstraat |
—
|
NE NERFINISHED |
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: Wiertzstraat | Statement: [Rue Wiertz, hasNameInDutch, Wiertzstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wiertzstraat Context triple: [Rue Wiertz, hasNameInDutch, Wiertzstraat]
-
A.
Wiertzstraat
chosen
Wiertzstraat is a street in Brussels, Belgium, located in the European Quarter near key European Union institutions.
-
B.
Valkenburgerstraat
Valkenburgerstraat is a street in central Amsterdam, Netherlands, located near the Waterlooplein area and served by the city’s metro network.
-
C.
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.
-
D.
Schupstraat
Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b6ddfc8190a23d291286f3fe42 |
completed | April 29, 2026, 6:22 a.m. |
Created at: April 17, 2026, 5:34 p.m.