Triple

T21285020
Position Surface form Disambiguated ID Type / Status
Subject Alblasserwaard E524632 entity
Predicate contains P35 FINISHED
Object Streefkerk NE NERFINISHED

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: Streefkerk | Statement: [Alblasserwaard, contains, Streefkerk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Streefkerk
Context triple: [Alblasserwaard, contains, Streefkerk]
  • A. Streefkerk chosen
    Streefkerk is a village in the Dutch province of South Holland, known for its location along the Lek River and its traditional windmills.
  • B. Oosterkerk
    Oosterkerk is a historic former church and notable architectural monument in the Dutch city of Hoorn.
  • C. Westerkerk
    Westerkerk is a prominent 17th-century Protestant church in central Amsterdam, renowned for its tall tower and association with Dutch Golden Age history.
  • D. Westerkerk
    Westerkerk is a historic Protestant church in the Dutch town of Enkhuizen, noted for its Renaissance architecture and prominent tower.
  • E. Stevenskerk
    Stevenskerk is a historic medieval church in Nijmegen, the Netherlands, known as the city's main and oldest church.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5171f6c8190a5d57201ede73811 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d658e08190ad2f267123d53ede completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:03 p.m.