Triple

T1655478
Position Surface form Disambiguated ID Type / Status
Subject Utrechtsestraat bridge E35788 entity
Predicate hasStreet P959 FINISHED
Object Utrechtsestraat E26500 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: Utrechtsestraat | Statement: [Utrechtsestraat bridge, hasStreet, Utrechtsestraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Utrechtsestraat
Context triple: [Utrechtsestraat bridge, hasStreet, Utrechtsestraat]
  • A. Utrechtsestraat chosen
    Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
  • B. Kalverstraat
    Kalverstraat is one of Amsterdam’s busiest and most famous shopping streets, known for its dense concentration of retail stores and central location.
  • C. Paleisstraat
    Paleisstraat is a central street in Amsterdam that runs alongside the Royal Palace and links Dam Square with the Jordaan area.
  • 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. Reguliersbreestraat
    Reguliersbreestraat is a well-known shopping and nightlife street in central Amsterdam, noted for its cinemas, bars, and vibrant atmosphere.
  • 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_69a8860568888190a32cd9f70acbba42 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90a8b597c81908a62b41718d85df6 completed March 5, 2026, 4:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae7ed8b7a08190a39f4b90fbf68cd9 completed March 9, 2026, 8:03 a.m.
Created at: March 4, 2026, 7:29 p.m.