Triple
T7620548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merksem |
E172479
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Schoten |
E679554
|
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: Schoten | Statement: [Merksem, hasBorderWith, Schoten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schoten Context triple: [Merksem, hasBorderWith, Schoten]
-
A.
Schoten
chosen
Schoten is a municipality in the Belgian province of Antwerp, known as a suburban residential area north of the city of Antwerp.
-
B.
Winschoten
Winschoten is a town in the northeast of the Netherlands known historically as a regional trade center and for its traditional windmills and Jewish heritage.
-
C.
Merchtem
Merchtem is a municipality in the Flemish Brabant province of Belgium, located in the Dutch-speaking Flanders region near Brussels.
-
D.
Nieuwenhoorn
Nieuwenhoorn is a village in the western Netherlands that forms part of the province of South Holland.
-
E.
Overpelt
Overpelt is a town in the Belgian province of Limburg, known for its green surroundings and local waterways.
- 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_69c8a212d0888190a40cdf32ef53d993 |
completed | March 29, 2026, 3:52 a.m. |
Created at: March 27, 2026, 3:55 p.m.