Triple

T222977
Position Surface form Disambiguated ID Type / Status
Subject Keizersgracht E4256 entity
Predicate parallelTo P1868 FINISHED
Object Prinsengracht E6262 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: Prinsengracht | Statement: [Keizersgracht, parallelTo, Prinsengracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prinsengracht
Context triple: [Keizersgracht, parallelTo, Prinsengracht]
  • A. Prinsengracht chosen
    Prinsengracht is one of Amsterdam’s main historic canals, known for its picturesque waterways, houseboats, and traditional canal houses.
  • B. Nieuwe Herengracht
    Nieuwe Herengracht is a canal in central Amsterdam that forms part of the city’s historic canal network and links to the Amstel River.
  • C. 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.
  • D. Singelgracht
    Singelgracht is a historic canal forming part of the outer ring of waterways around Amsterdam’s city center.
  • E. Reguliersgracht
    Reguliersgracht is a picturesque canal in Amsterdam’s historic center, renowned for its classic canal houses and iconic series of arched bridges.
  • 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_69a2573508588190b522c2476d91acfe completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25c705fd88190bfee7f5e1f7cee17 completed Feb. 28, 2026, 3:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3914b6cb08190ae5413f46aedc23f completed March 1, 2026, 1:07 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.