Triple

T7682083
Position Surface form Disambiguated ID Type / Status
Subject Hugo van der Goes E174019 entity
Predicate deathPlace P21 FINISHED
Object Roode Klooster E119839 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: Roode Klooster | Statement: [Hugo van der Goes, deathPlace, Roode Klooster]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roode Klooster
Context triple: [Hugo van der Goes, deathPlace, Roode Klooster]
  • A. Reguliersklooster
    Reguliersklooster was a former monastery in Amsterdam whose presence and influence gave its name to several nearby streets and canals.
  • B. Grijpskerk
    Grijpskerk is a village in the Dutch province of Groningen, known historically as a local agricultural and railway hub.
  • C. Ridderkerk
    Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
  • D. Oostkerk
    Oostkerk is a historic domed Protestant church in the Dutch city of Middelburg, known for its distinctive centralised Baroque architecture.
  • E. Abbey of Middelburg chosen
    The Abbey of Middelburg is a historic monastic complex in the Dutch city of Middelburg, notable for its medieval architecture and prominent church towers.
  • 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_69c6995840408190a19de6c51090f46f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c70201387c8190afc8479b5a9e21e8 completed March 27, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a25304b88190920c2e4908925ce2 completed March 29, 2026, 3:53 a.m.
Created at: March 27, 2026, 4:01 p.m.