Triple
T20678561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic city center of Middelburg |
E508227
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Oostkerk |
—
|
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: Oostkerk | Statement: [historic city center of Middelburg, hasLandmark, Oostkerk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oostkerk Context triple: [historic city center of Middelburg, hasLandmark, Oostkerk]
-
A.
Oostkerk
chosen
Oostkerk is a historic domed Protestant church in the Dutch city of Middelburg, known for its distinctive centralised Baroque architecture.
-
B.
Oosterkerk
Oosterkerk is a historic former church and notable architectural monument in the Dutch city of Hoorn.
-
C.
Grijpskerk
Grijpskerk is a village in the Dutch province of Groningen, known historically as a local agricultural and railway hub.
-
D.
Streefkerk
Streefkerk is a village in the Dutch province of South Holland, known for its location along the Lek River and its traditional windmills.
-
E.
Noorderkerk
Noorderkerk is a 17th-century Protestant church in Amsterdam, notable for its distinctive Dutch Renaissance architecture and central role in the historic Jordaan district.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea354f0819094e9ee8d3adaa221 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 11:44 a.m.