Triple
T12116570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grootegast |
E288576
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Zuidhorn |
—
|
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: Zuidhorn | Statement: [Grootegast, borderedBy, Zuidhorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zuidhorn Context triple: [Grootegast, borderedBy, Zuidhorn]
-
A.
Zuidhorn
chosen
Zuidhorn is a village and former municipality in the province of Groningen in the northern Netherlands, known for its rural character and proximity to the city of Groningen.
-
B.
Sneek
Sneek is a historic Dutch city known for its waterways, sailing culture, and the iconic Waterpoort gate.
-
C.
Hulst
Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
-
D.
Nieuwendam
Nieuwendam is a historic neighborhood in the northern part of Amsterdam, known for its former village character and waterfront location along the IJ.
-
E.
Spaarndam
Spaarndam is a historic Dutch village in North Holland, known for its old sluices and dikes along the river Spaarne and its traditional waterfront charm.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9156921dc8190aa132b0ab3a7c184 |
completed | April 10, 2026, 3:21 p.m. |
Created at: April 8, 2026, 9:49 p.m.