Triple
T15110008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laarbeek |
E360885
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Lieshout |
E726197
|
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: Lieshout | Statement: [Laarbeek, hasSettlement, Lieshout]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lieshout Context triple: [Laarbeek, hasSettlement, Lieshout]
-
A.
Lieshout
chosen
Lieshout is a village in the Dutch province of North Brabant, known for its rural character and the Bavaria brewery.
-
B.
Oostduinkerke
Oostduinkerke is a coastal village in West Flanders, Belgium, known for its North Sea beaches and traditional shrimp fishing on horseback.
-
C.
Torhout
Torhout is a small city in West Flanders, Belgium, known for its educational institutions and its location near Bruges.
-
D.
Terneuzen
Terneuzen is a port city and municipality in the southwestern Netherlands, known for its location on the Western Scheldt and its role in shipping access to the port of Ghent.
-
E.
Slochteren
Slochteren is a village and former municipality in the province of Groningen in the Netherlands, historically known for its large natural gas field.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058c04f481909deeac0271d961b6 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff78dab488190a89b9eb4f648b36c |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 3:05 a.m.