Triple

T7262431
Position Surface form Disambiguated ID Type / Status
Subject Mint Square E159686 entity
Predicate hasNearbyStreet P8235 FINISHED
Object Reguliersbreestraat E186454 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: Reguliersbreestraat | Statement: [Mint Square, hasNearbyStreet, Reguliersbreestraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reguliersbreestraat
Context triple: [Mint Square, hasNearbyStreet, Reguliersbreestraat]
  • A. Reguliersbreestraat chosen
    Reguliersbreestraat is a well-known shopping and nightlife street in central Amsterdam, noted for its cinemas, bars, and vibrant atmosphere.
  • B. Reguliersdwarsstraat
    Reguliersdwarsstraat is a well-known street in central Amsterdam, noted for its vibrant nightlife, bars, and LGBTQ+ venues.
  • C. Heemstedestraat
    Heemstedestraat is a metro station in Amsterdam that serves as a stop on the city’s rapid transit network.
  • D. 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.
  • 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_69c68838f9948190875fd60b2351230c completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eac8bc908190b0e4da5474ecb62f completed March 27, 2026, 8:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c827604a808190a362734e864123aa completed March 28, 2026, 7:09 p.m.
Created at: March 27, 2026, 2:57 p.m.