Triple
T11011558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gooi en Vechtstreek |
E260259
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Weesp |
E548815
|
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: Weesp | Statement: [Gooi en Vechtstreek, contains, Weesp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weesp Context triple: [Gooi en Vechtstreek, contains, Weesp]
-
A.
Weesp
chosen
Weesp is a historic town in the province of North Holland in the Netherlands, known for its canals, fortified structures, and traditional Dutch architecture.
-
B.
Oosterhout
Oosterhout is a town and municipality in the southern Netherlands known for its historic monasteries and proximity to the city of Breda.
-
C.
Oisterwijk
Oisterwijk is a town in the Dutch province of North Brabant known for its historic center and surrounding forest and fen landscapes.
-
D.
Roosendaal
Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian border.
-
E.
Valkenswaard
Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797899a388190aa8fe813eac4dba7 |
completed | April 9, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa11c81f481909129eef69e47d079 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 8, 2026, 9:25 p.m.