Triple
T20885304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldambt |
E514261
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Heiligerlee |
—
|
NE NERFINISHED |
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: Heiligerlee | Statement: [Oldambt, contains, Heiligerlee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heiligerlee Context triple: [Oldambt, contains, Heiligerlee]
-
A.
Heiligerlee
chosen
Heiligerlee is a small village in the Dutch province of Groningen, known historically for the 1568 Battle of Heiligerlee, one of the first battles of the Eighty Years' War.
-
B.
Harksheide
Harksheide was a former municipality in Schleswig-Holstein, Germany, that later became part of the city of Norderstedt.
-
C.
Drimmelen
Drimmelen is a municipality and village in the southern Netherlands, known for its historic harbor and as a gateway to the Biesbosch National Park.
-
D.
Ysselsteyn
Ysselsteyn is a village in the Dutch province of Limburg, known for its large German war cemetery and agricultural surroundings.
-
E.
Lindenholt
Lindenholt is a residential neighborhood in the Dutch city of Nijmegen, known as part of the larger Dukenburg area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 12:46 p.m.