Triple
T3472505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borsele |
E73295
|
entity |
| Predicate | hasVillage |
P4011
|
FINISHED |
| Object | Lewedorp |
E358223
|
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: Lewedorp | Statement: [Borsele, hasVillage, Lewedorp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lewedorp Context triple: [Borsele, hasVillage, Lewedorp]
-
A.
Lewedorp
chosen
Lewedorp is a small village in the Dutch province of Zeeland, located on the former island of Zuid-Beveland.
-
B.
Beinsdorp
Beinsdorp is a small village in the Dutch province of North Holland, situated within the municipality of Haarlemmermeer.
-
C.
Leusden
Leusden is a Dutch town and municipality in the central Netherlands, known for its green residential character and proximity to the city of Amersfoort.
-
D.
Rijsbergen
Rijsbergen is a village in the Dutch province of North Brabant, located near the Belgian border and known for its rural character.
-
E.
Numansdorp
Numansdorp is a village in the western Netherlands known for its rural character and location on the island of Hoeksche Waard.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3cc8488190b97c732e3f600a90 |
completed | March 8, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eebbef8c8190ad00760312e40924 |
completed | March 27, 2026, 8:55 p.m. |
Created at: March 8, 2026, 3:17 p.m.