Triple
T22615826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Heusden |
E558142
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Vlijmen |
—
|
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: Vlijmen | Statement: [municipality of Heusden, contains, Vlijmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vlijmen Context triple: [municipality of Heusden, contains, Vlijmen]
-
A.
Vlijmen
chosen
Vlijmen is a town in the Dutch province of North Brabant, known historically as part of the Land van Heusden region.
-
B.
Vlijtingen
Vlijtingen is a village in the Belgian province of Limburg that forms part of the municipality of Riemst.
-
C.
Geervliet
Geervliet is a small historic town in the western Netherlands, located in the province of South Holland.
-
D.
Veulen
Veulen is a small village in the Belgian province of Limburg, forming part of the municipality of Heers.
-
E.
Vilsteren
Vilsteren is a small rural hamlet in the Dutch province of Overijssel, known for its historic estates and scenic landscape along the river Vecht.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167edec2481909c2f06607b3cb8f6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:59 p.m.