Triple

T470332
Position Surface form Disambiguated ID Type / Status
Subject Brouwersgracht E8540 entity
Predicate hasNotableIntersection P13379 FINISHED
Object Herengracht E3946 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: Herengracht | Statement: [Brouwersgracht, hasNotableIntersection, Herengracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Herengracht
Context triple: [Brouwersgracht, hasNotableIntersection, Herengracht]
  • A. Herengracht chosen
    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.
  • B. 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.
  • C. Prinsengracht
    Prinsengracht is one of Amsterdam’s main historic canals, known for its picturesque waterways, houseboats, and traditional canal houses.
  • D. 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.
  • 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_69a2e7f3aeb48190a19453e3a043f486 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2f01ec5148190b74e1727712f1163 completed Feb. 28, 2026, 1:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69a48a7675a08190985e76c3d3bbd495 completed March 1, 2026, 6:50 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.