Triple
T15337380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostkapelle |
E366701
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Domburg |
E361424
|
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: Domburg | Statement: [Oostkapelle, locatedNear, Domburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Domburg Context triple: [Oostkapelle, locatedNear, Domburg]
-
A.
Domburg
Domburg is a town in Suriname located within the Wanica District, known for its residential character and proximity to the capital, Paramaribo.
-
B.
Domburg
chosen
Domburg is a coastal resort town and one of the oldest seaside destinations in the Dutch province of Zeeland.
-
C.
Gaasperdam
Gaasperdam is a residential neighborhood in the southeastern part of Amsterdam known for its green spaces and proximity to the Gaasperplas recreational area.
-
D.
Alblasserdam
Alblasserdam is a town and municipality in the western Netherlands, situated along the Noord River and known for its proximity to the Kinderdijk windmills.
-
E.
Hoogezand
Hoogezand is a town in the Dutch province of Groningen that serves as the administrative center of the municipality of Midden-Groningen.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01f11b88819089342e8b088bc95e |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.