Triple
T4088263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampen |
E87640
|
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: [Kampen, hasReligiousBuilding, Bovenkerk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bovenkerk Context triple: [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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca899008190b5ada98bdb79639f |
completed | March 9, 2026, 5 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e4e76cf881909e45c3652a372a70 |
completed | March 28, 2026, 2:25 p.m. |
Created at: March 9, 2026, 3:39 p.m.