Triple

T12065479
Position Surface form Disambiguated ID Type / Status
Subject Hanseatic city of Kampen E287282 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Bovenkerk E653718 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: Bovenkerk | Statement: [Hanseatic city of Kampen, hasReligiousBuilding, Bovenkerk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bovenkerk
Context triple: [Hanseatic city of Kampen, hasReligiousBuilding, Bovenkerk]
  • A. Bovenkerk chosen
    Bovenkerk is a prominent historic church in the Dutch city of Kampen, known for its Gothic architecture and significant cultural and religious heritage.
  • B. Grijpskerke
    Grijpskerke is a village in the Dutch province of Zeeland, located on the former island of Walcheren.
  • C. Oldekerk
    Oldekerk is a village in the Dutch province of Groningen, known as a small rural community within the municipality of Westerkwartier.
  • D. Kleverskerke
    Kleverskerke is a small village in the Dutch province of Zeeland, located in the southwestern Netherlands.
  • E. Hoedekenskerke
    Hoedekenskerke is a small village in the Dutch province of Zeeland, known for its rural character and location along the Western Scheldt.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90440dd988190ae2b80367aceb6f7 completed April 10, 2026, 2:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd191f84bc819096d6cc6167732a98 completed May 7, 2026, 10:58 p.m.
Created at: April 8, 2026, 9:48 p.m.