Triple

T22878609
Position Surface form Disambiguated ID Type / Status
Subject Koepel Church in Amsterdam E567394 entity
Predicate hasNameInDutch P13254 FINISHED
Object Koepelkerk 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: Koepelkerk | Statement: [Koepel Church in Amsterdam, hasNameInDutch, Koepelkerk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koepelkerk
Context triple: [Koepel Church in Amsterdam, hasNameInDutch, Koepelkerk]
  • A. Koepelkerk chosen
    Koepelkerk is a historic domed Lutheran church in Amsterdam, Netherlands, noted for its distinctive round architecture and prominent copper dome.
  • B. Stulpkerk
    Stulpkerk is a historic church located in the village of Lage Vuursche in the Netherlands.
  • C. Stephanuskerk
    Stephanuskerk is a historic Dutch church dedicated to Saint Stephen, notable for its traditional architecture and cultural significance in the Netherlands.
  • D. Grote of Barbarakerk
    Grote of Barbarakerk is a historic Gothic church in Culemborg, Netherlands, known for its prominent tower and role as a central religious and cultural monument in the town.
  • E. Grote Kerk
    Grote Kerk is a historic medieval church in Dordrecht, Netherlands, renowned for its imposing Gothic architecture and prominent tower.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f5a26f4819086ede6d85a2ab2bf completed April 29, 2026, 3:47 a.m.
Created at: April 17, 2026, 3:39 p.m.