Triple

T6302149
Position Surface form Disambiguated ID Type / Status
Subject Vijzelgracht metro station E141280 entity
Predicate hasEntranceNear P3449 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: [Vijzelgracht metro station, hasEntranceNear, Vijzelstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vijzelstraat
Context triple: [Vijzelgracht metro station, hasEntranceNear, 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. 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. Lepelstraat
    Lepelstraat is a village in the Dutch province of North Brabant that forms part of the municipality of Bergen op Zoom.
  • E. Domstraat
    Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645cfca88190ace060ef5b0e00e8 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c64ba5b0bc8190aefa07c77c99be83 completed March 27, 2026, 9:19 a.m.
Created at: March 22, 2026, 4:27 p.m.