Triple
T12836607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eemsmond |
E306931
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Bedum |
—
|
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: Bedum | Statement: [Eemsmond, sharesBorderWith, Bedum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bedum Context triple: [Eemsmond, sharesBorderWith, Bedum]
-
A.
Bedum
chosen
Bedum is a former municipality and village in the province of Groningen in the Netherlands, now part of the larger municipality of Het Hogeland.
-
B.
Schagen
Schagen is a historic market town and municipality in the province of North Holland in the Netherlands, known for its traditional West Frisian culture and regional role as a local center.
-
C.
Deurne
Deurne is a municipality in the Dutch province of North Brabant, known for its rural character and historic peat extraction areas.
-
D.
Deurne
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
E.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff015f4819090070a01f3938acc |
completed | April 10, 2026, 9:47 p.m. |
Created at: April 9, 2026, 5:35 p.m.