Triple

T3109535
Position Surface form Disambiguated ID Type / Status
Subject Jordaan E64916 entity
Predicate traversedBy P225 FINISHED
Object Lauriergracht E279037 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: Lauriergracht | Statement: [Jordaan, traversedBy, Lauriergracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauriergracht
Context triple: [Jordaan, traversedBy, Lauriergracht]
  • A. Brouwersgracht
    Brouwersgracht is a picturesque historic canal in Amsterdam, renowned for its traditional canal houses, bridges, and central location in the city’s canal belt.
  • B. Reguliersgracht
    Reguliersgracht is a picturesque canal in Amsterdam’s historic center, renowned for its classic canal houses and iconic series of arched bridges.
  • C. Oude Gracht
    Oude Gracht is a historic canal running through the center of Utrecht, Netherlands, known for its unique wharf cellars, waterside terraces, and medieval charm.
  • D. Westlandgracht
    Westlandgracht is a canal in Amsterdam, Netherlands, forming part of the city’s western waterway network.
  • E. Lindengracht chosen
    Lindengracht is a historic canal and street in Amsterdam’s Jordaan district, known for its traditional architecture and lively local markets.
  • 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_69ad857eeaf48190b34ebfdaa7a264cf completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada2a0ab2481908db50738ec3ad0fb completed March 8, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b261eb2e708190b192574d3f5862e6 completed March 12, 2026, 6:49 a.m.
Created at: March 8, 2026, 3:04 p.m.