Triple
T14087439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midden-Drenthe |
E339033
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Hooghalen |
E983739
|
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: Hooghalen | Statement: [Midden-Drenthe, containsSettlement, Hooghalen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hooghalen Context triple: [Midden-Drenthe, containsSettlement, Hooghalen]
-
A.
Hooghalen
chosen
Hooghalen is a village in the Dutch province of Drenthe, known for its proximity to the former Westerbork transit camp from World War II.
-
B.
Holleken
Holleken is a local railway station serving the suburban area near Brussels, Belgium.
-
C.
Hoogmade
Hoogmade is a small village in the Dutch province of South Holland, known for its rural character and location within the municipality of Kaag en Braassem.
-
D.
Hackenholt
Hackenholt is a German surname most notably associated with Lorenz Hackenholt, an SS officer involved in the Nazi extermination camps during World War II.
-
E.
Bonteheuwel
Bonteheuwel is a residential suburb of Cape Town, South Africa, located on the Cape Flats and known for its working-class community and apartheid-era history.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0a5c9948190805c2e687c8809ff |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:21 p.m.