Triple
T2666684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westerkwartier |
E55651
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object |
Oldehove
Oldehove is a village in the Dutch province of Groningen, known for its rural character and historic church.
|
E293080
|
NE FINISHED |
How this triple was built (4 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: Oldehove | Statement: [Westerkwartier, containsSettlement, Oldehove]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oldehove Context triple: [Westerkwartier, containsSettlement, Oldehove]
-
A.
Oldenzaal
Oldenzaal is a historic city in the eastern Netherlands known for its medieval center and location near the German border in the province of Overijssel.
-
B.
Holendrecht
Holendrecht is a metro station in Amsterdam serving the southeastern part of the city, including the nearby academic hospital and university campus.
-
C.
Haaksbergen
Haaksbergen is a town in the eastern Netherlands, near the German border, known for its rural surroundings and cross-border ties with neighboring German communities.
-
D.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
-
E.
Begijnhof
Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Oldehove Triple: [Westerkwartier, containsSettlement, Oldehove]
Generated description
Oldehove is a village in the Dutch province of Groningen, known for its rural character and historic church.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Oldehove Target entity description: Oldehove is a village in the Dutch province of Groningen, known for its rural character and historic church.
-
A.
Oldenzaal
Oldenzaal is a historic city in the eastern Netherlands known for its medieval center and location near the German border in the province of Overijssel.
-
B.
Holendrecht
Holendrecht is a metro station in Amsterdam serving the southeastern part of the city, including the nearby academic hospital and university campus.
-
C.
Haaksbergen
Haaksbergen is a town in the eastern Netherlands, near the German border, known for its rural surroundings and cross-border ties with neighboring German communities.
-
D.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
-
E.
Begijnhof
Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
- F. None of above. chosen
Provenance (5 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd97040e48190b0a87489f108810e |
completed | March 7, 2026, 7:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb6775b008190a59e480516c3ef41 |
completed | March 10, 2026, 6:13 a.m. |
| NEDg | Description generation | batch_69afb75ea498819089c79e63052e9696 |
completed | March 10, 2026, 6:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afb83ba6dc8190931d691d3e354bd7 |
completed | March 10, 2026, 6:20 a.m. |
Created at: March 6, 2026, 9:54 p.m.