Triple

T7262428
Position Surface form Disambiguated ID Type / Status
Subject Mint Square E159686 entity
Predicate hasNearbyStreet P8235 FINISHED
Object Kalverstraat E66237 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: Kalverstraat | Statement: [Mint Square, hasNearbyStreet, Kalverstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalverstraat
Context triple: [Mint Square, hasNearbyStreet, Kalverstraat]
  • A. Kalverstraat chosen
    Kalverstraat is one of Amsterdam’s busiest and most famous shopping streets, known for its dense concentration of retail stores and central location.
  • B. Koningsstraat
    Koningsstraat is a major central street in Brussels, Belgium, known for its straight, ceremonial layout and its role connecting key royal and administrative landmarks.
  • C. Servetstraat
    Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
  • D. Paleisstraat
    Paleisstraat is a central street in Amsterdam that runs alongside the Royal Palace and links Dam Square with the Jordaan area.
  • E. Utrechtsestraat
    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.
  • 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_69c810bb0d808190b6ade5592fce2c15 completed March 28, 2026, 5:32 p.m.
Created at: March 27, 2026, 2:57 p.m.