Triple

T18913097
Position Surface form Disambiguated ID Type / Status
Subject Vijzelstraat crossing E462653 entity
Predicate street P959 FINISHED
Object Vijzelstraat 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: Vijzelstraat | Statement: [Vijzelstraat crossing, street, Vijzelstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vijzelstraat
Context triple: [Vijzelstraat crossing, street, 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. Schupstraat
    Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
  • C. Zadelstraat
    Zadelstraat is a historic shopping street in the center of Utrecht, Netherlands, known for its old buildings, boutiques, and cafés leading toward the Dom Tower.
  • D. Roetersstraat
    Roetersstraat is a street in Amsterdam that runs through the University of Amsterdam’s Roeterseiland campus area.
  • 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.
  • 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_69d8dcfdbbb881909964fa5a75bd0b48 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c624516c81909e6bf04707d3c71c completed April 20, 2026, 6:22 a.m.
Created at: April 10, 2026, 11:58 a.m.