Triple

T1221412
Position Surface form Disambiguated ID Type / Status
Subject Reguliersgracht E26229 entity
Predicate connectsTo P845 FINISHED
Object Keizersgracht E4256 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: Keizersgracht | Statement: [Reguliersgracht, connectsTo, Keizersgracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keizersgracht
Context triple: [Reguliersgracht, connectsTo, Keizersgracht]
  • A. Keizersgracht chosen
    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.
  • B. Prinsengracht
    Prinsengracht is one of Amsterdam’s main historic canals, known for its picturesque waterways, houseboats, and traditional canal houses.
  • C. 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.
  • D. Herengracht
    Herengracht is one of Amsterdam’s most famous and historic canals, renowned for its elegant 17th-century canal houses and central role in the city’s canal belt.
  • E. Singelgracht
    Singelgracht is a historic canal forming part of the outer ring of waterways around Amsterdam’s city center.
  • 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_69a49484688c8190a1bf285eb396a8b6 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be206c108190bb8a5d44fc516c98 completed March 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad67f9b0dc8190a5b38450c227eac5 completed March 8, 2026, 12:13 p.m.
Created at: March 1, 2026, 7:47 p.m.