Triple
T11829640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorpskerk in Wassenaar |
E281352
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Wassenaar |
E174773
|
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: Wassenaar | Statement: [Dorpskerk in Wassenaar, locatedIn, Wassenaar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wassenaar Context triple: [Dorpskerk in Wassenaar, locatedIn, Wassenaar]
-
A.
Wassenaar
chosen
Wassenaar is an affluent coastal town in the western Netherlands known for its wooded estates, beaches, and role as a residential area for diplomats and expatriates.
-
B.
Yerseke
Yerseke is a Dutch village in the province of Zeeland, best known for its mussel and oyster farming along the Eastern Scheldt.
-
C.
Vandamm
Vandamm is a surname, often a variant spelling of "van Damm," associated with various individuals in arts, entertainment, and other fields.
-
D.
Esens
Esens is a small historic town in Lower Saxony, Germany, known for its coastal North Sea location and traditional East Frisian character.
-
E.
Wateringen
Wateringen is a town in the western Netherlands that forms part of the municipality of Westland 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62b75dc8190b27d24e46a262a11 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f2812007dc81908e56fd47b2a94836 |
completed | April 29, 2026, 10:07 p.m. |
Created at: April 8, 2026, 9:43 p.m.