Triple

T4479066
Position Surface form Disambiguated ID Type / Status
Subject Pieter Saenredam E100082 entity
Predicate placeOfDeath P21 FINISHED
Object Haarlem E80096 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: Haarlem | Statement: [Pieter Saenredam, placeOfDeath, Haarlem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haarlem
Context triple: [Pieter Saenredam, placeOfDeath, Haarlem]
  • A. Haarlem chosen
    Haarlem is a historic Dutch city in the province of North Holland, known for its medieval architecture, cultural heritage, and role as a regional center near Amsterdam.
  • B. Utrecht
    Utrecht is a historic city and province in the central Netherlands, known for its medieval old town, canals, and role as a religious and cultural center.
  • C. Nijmegen
    Nijmegen is a historic Dutch city near the German border that played a crucial strategic role during World War II, particularly in the Allied advance in 1944.
  • D. Rijswijk
    Rijswijk is a town in the western Netherlands, near The Hague, historically notable as the site where the 1697 Treaty of Rijswijk ended the Nine Years' War.
  • E. Hilversum
    Hilversum is a Dutch city known as the country’s main media and broadcasting center, located in the province of North Holland.
  • 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_69b34553cbe48190afa8ac1cac285b86 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356db0a008190ad39b68efc095b8d completed March 13, 2026, 12:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f67c3a0881909f24d85d74e4c061 completed April 9, 2026, 12:44 a.m.
Created at: March 12, 2026, 11:35 p.m.