Triple

T12826612
Position Surface form Disambiguated ID Type / Status
Subject Nieuwezijds Voorburgwal E306667 entity
Predicate connects P390 FINISHED
Object Raadhuisstraat E360453 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: Raadhuisstraat | Statement: [Nieuwezijds Voorburgwal, connects, Raadhuisstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raadhuisstraat
Context triple: [Nieuwezijds Voorburgwal, connects, Raadhuisstraat]
  • A. Raadhuisstraat chosen
    Raadhuisstraat is a central street in Amsterdam, Netherlands, known for connecting Dam Square to the Jordaan district and for its historic architecture and shops.
  • B. Schupstraat
    Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
  • C. Domstraat
    Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
  • D. Rozenstraat
    Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
  • E. Breidelstraat
    Breidelstraat is a historic street in the center of Bruges, Belgium, connecting the Markt square with other medieval lanes and lined with traditional Flemish architecture.
  • 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_69d7bdf52b94819096d6f0ba4ab50a98 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96fae51608190a50970bd038359a5 completed April 10, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5bc5f688190a6fd3716c8266b2c completed May 3, 2026, 7:14 a.m.
Created at: April 9, 2026, 5:33 p.m.