Triple
T7620461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berchem |
E172477
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Wilrijk |
E201858
|
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: Wilrijk | Statement: [Berchem, borders, Wilrijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilrijk Context triple: [Berchem, borders, Wilrijk]
-
A.
Wilrijk
chosen
Wilrijk is a southern district of the Belgian city of Antwerp, known for its residential character and green spaces.
-
B.
La Hulpe
La Hulpe is a small, affluent municipality in Walloon Brabant, Belgium, known for its green surroundings and the Château de La Hulpe within the Solvay Regional Estate.
-
C.
Geervliet
Geervliet is a small historic town in the western Netherlands, located in the province of South Holland.
-
D.
Groene Hart
Groene Hart is a largely rural, green area in the western Netherlands, situated between major cities like Amsterdam, Rotterdam, The Hague, and Utrecht, known for its open landscapes, peat meadows, and nature conservation.
-
E.
Weerde
Weerde is a village in the Flemish Brabant province of Belgium, known as a residential suburb within the municipality of Zemst.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa62870c8190b17f44eb7a3ff2ad |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c868789618819094010e60ef73fdfd |
completed | March 28, 2026, 11:47 p.m. |
Created at: March 27, 2026, 3:55 p.m.