Triple

T12826607
Position Surface form Disambiguated ID Type / Status
Subject Nieuwezijds Voorburgwal E306667 entity
Predicate parallelTo P1868 FINISHED
Object Spuistraat E305255 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: Spuistraat | Statement: [Nieuwezijds Voorburgwal, parallelTo, Spuistraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spuistraat
Context triple: [Nieuwezijds Voorburgwal, parallelTo, Spuistraat]
  • A. Spuistraat chosen
    Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
  • B. Stoofstraat
    Stoofstraat is a small, historic street in central Brussels, Belgium, located near the famous Manneken Pis statue.
  • C. Rijfstraat
    Rijfstraat is a key street in Antwerp’s Diamond District, known for its concentration of diamond-related businesses and trade.
  • D. Schupstraat
    Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
  • E. Hartenstraat
    Hartenstraat is one of the small, picturesque shopping streets in Amsterdam’s historic Negen Straatjes (Nine Streets) district, known for its boutiques, cafés, and canal-side charm.
  • 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_69f6eac829ec8190bea8efdc93151aa0 completed May 3, 2026, 6:27 a.m.
Created at: April 9, 2026, 5:33 p.m.