Triple
T7891106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aalst dialect |
E183235
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Aalst |
E527486
|
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: Aalst | Statement: [Aalst dialect, spokenIn, Aalst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aalst Context triple: [Aalst dialect, spokenIn, Aalst]
-
A.
Aalst
chosen
Aalst is a historic city in the Belgian province of East Flanders, known for its textile industry and famous annual carnival.
-
B.
Wommelgem
Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
C.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
-
D.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
-
E.
Hasselt
Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39ee137081908e87e35016c3a176 |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf275f49f48190ad92d5aaebaac4d0 |
completed | April 3, 2026, 2:35 a.m. |
Created at: March 30, 2026, 5 p.m.