Triple
T19507232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mook |
E488053
|
entity |
| Predicate | hasNearbyFeature |
P350
|
FINISHED |
| Object | Mookerheide |
—
|
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: Mookerheide | Statement: [Mook, hasNearbyFeature, Mookerheide]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mookerheide Context triple: [Mook, hasNearbyFeature, Mookerheide]
-
A.
Mookerheide
chosen
Mookerheide is a heathland and nature reserve in the Dutch province of Limburg, known for its scenic landscapes and historical World War II significance.
-
B.
Molenhoek
Molenhoek is a village in the Dutch province of Limburg, known for its proximity to Mook and its location near the Maas River and the German border.
-
C.
Mookerplas
Mookerplas is a recreational lake in the Dutch province of Limburg, popular for swimming, water sports, and nature activities.
-
D.
Harksheide
Harksheide was a former municipality in Schleswig-Holstein, Germany, that later became part of the city of Norderstedt.
-
E.
Millingerwaard
Millingerwaard is a riverine nature reserve along the Waal in the Netherlands, known for its restored floodplain landscapes, grazing herds, and rich biodiversity.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635130e708190bb3d70e1abbade2a |
completed | April 20, 2026, 2:15 p.m. |
Created at: April 10, 2026, 1:40 p.m.