Triple

T23318268
Position Surface form Disambiguated ID Type / Status
Subject Marnixstraat E590773 entity
Predicate runsAlong P416 FINISHED
Object Singelgracht NE NERFINISHED

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: Singelgracht | Statement: [Marnixstraat, runsAlong, Singelgracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Singelgracht
Context triple: [Marnixstraat, runsAlong, Singelgracht]
  • A. Singelgracht chosen
    Singelgracht is a historic canal forming part of the outer ring of waterways around Amsterdam’s city center.
  • B. Lindengracht
    Lindengracht is a historic canal and street in Amsterdam’s Jordaan district, known for its traditional architecture and lively local markets.
  • C. Elandsgracht
    Elandsgracht is a notable street in Amsterdam’s Jordaan neighborhood, known for its local shops, cafes, and historic atmosphere.
  • D. Reguliersgracht
    Reguliersgracht is a picturesque canal in Amsterdam’s historic center, renowned for its classic canal houses and iconic series of arched bridges.
  • E. Keizersgracht
    Keizersgracht is one of Amsterdam’s main historic canals, renowned for its grand 17th-century canal houses and central role in the city’s UNESCO-listed canal belt.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1978372948190bad066893c4e0768 completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:07 p.m.