Triple

T2317392
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam-Centrum E51096 entity
Predicate contains P35 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: [Amsterdam-Centrum, contains, Prinsengracht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prinsengracht
Context triple: [Amsterdam-Centrum, contains, 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. Lindengracht
    Lindengracht is a historic canal and street in Amsterdam’s Jordaan district, known for its traditional architecture and lively local markets.
  • 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_69a88b074b908190ae983dbca7757d88 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc62df2048190ac7a5ebc0a4139b2 completed March 7, 2026, 6:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69afa03e7b6c81909e61671bd4435723 completed March 10, 2026, 4:38 a.m.
Created at: March 4, 2026, 7:49 p.m.