Triple
T22150911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonheiden |
E547408
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Rijmenam |
E1522150
|
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: Rijmenam | Statement: [Bonheiden, hasSubdivision, Rijmenam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rijmenam Context triple: [Bonheiden, hasSubdivision, Rijmenam]
-
A.
Rijmenam
chosen
Rijmenam is a village in the Belgian province of Antwerp, known as a sub-municipality of Bonheiden.
-
B.
Rijmen
Rijmen is a Dutch-language surname most notably borne by Belgian cryptographer Vincent Rijmen, co-designer of the AES encryption algorithm.
-
C.
Heurne
Heurne is a small village in the municipality of Aalten in the Dutch province of Gelderland.
-
D.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
E.
Wiekevorst
Wiekevorst is a village in the Belgian province of Antwerp that forms part of the municipality of Heist-op-den-Berg.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f37dac8190a7cecb12f4271515 |
completed | April 28, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a9eb8d398819086031725209b6712 |
completed | May 18, 2026, 5:08 a.m. |
Created at: April 16, 2026, 8:33 p.m.