Triple
T17053134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellendoorn |
E413750
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Wierden |
—
|
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: Wierden | Statement: [Hellendoorn, borders, Wierden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wierden Context triple: [Hellendoorn, borders, Wierden]
-
A.
Wierden
chosen
Wierden is a municipality and town in the Dutch province of Overijssel, located in the Twente region of the Netherlands.
-
B.
Oosterwijtwerd
Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
-
C.
Yerseke
Yerseke is a Dutch village in the province of Zeeland, best known for its mussel and oyster farming along the Eastern Scheldt.
-
D.
Nieuwendijk
Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
-
E.
Roderwolde
Roderwolde is a small rural village in the Dutch province of Drenthe, known for its historic church and traditional countryside landscape.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa491008190ad013ee37532aa51 |
completed | April 18, 2026, 7:25 p.m. |
Created at: April 10, 2026, 5:34 a.m.