Triple
T11117215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eenrum |
E262916
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Wehe-den Hoorn |
E266404
|
NE FINISHED |
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: Wehe-den Hoorn | Statement: [Eenrum, hasNearbySettlement, Wehe-den Hoorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wehe-den Hoorn Context triple: [Eenrum, hasNearbySettlement, Wehe-den Hoorn]
-
A.
Wehe-den Hoorn
chosen
Wehe-den Hoorn is a small village in the Dutch province of Groningen, known for its historic churches and traditional rural character.
-
B.
Westzaan
Westzaan is a village in the Dutch province of North Holland, known for its historic peatlands and traditional Zaan region architecture.
-
C.
Hoendiep
Hoendiep is a canal in the Dutch province of Groningen that serves as an important regional waterway and transport route.
-
D.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
-
E.
Zwartewaal
Zwartewaal is a small village in the western Netherlands, located in the province of South Holland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af638b08190b7ade5eb0cab6b75 |
completed | April 9, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d8084a88190918f1f94ca0119ed |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.