Triple
T19695921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N388 |
E472958
|
entity |
| Predicate | connectsSettlement |
P8239
|
FINISHED |
| Object | Grijpskerk |
—
|
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: Grijpskerk | Statement: [N388, connectsSettlement, Grijpskerk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grijpskerk Context triple: [N388, connectsSettlement, Grijpskerk]
-
A.
Grijpskerk
chosen
Grijpskerk is a village in the Dutch province of Groningen, known historically as a local agricultural and railway hub.
-
B.
Buurkerk
Buurkerk is a historic medieval church in Utrecht, Netherlands, notable for its Gothic architecture and former role as one of the city’s main parish churches.
-
C.
Oostkerk
Oostkerk is a historic domed Protestant church in the Dutch city of Middelburg, known for its distinctive centralised Baroque architecture.
-
D.
St Joriskerk
St Joriskerk is a historic church in the Dutch town of Bredevoort, known for its traditional architecture and cultural significance in the region.
-
E.
Leegkerk
Leegkerk is a small village in the province of Groningen in the Netherlands, known for its historic rural character and proximity to the city of Groningen.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642147c3c8190a4c788e4bb48fe11 |
completed | April 20, 2026, 3:11 p.m. |
Created at: April 10, 2026, 1:46 p.m.