Triple
T21372324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geldern |
E527096
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Straelen |
—
|
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: Straelen | Statement: [Geldern, locatedNear, Straelen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Straelen Context triple: [Geldern, locatedNear, Straelen]
-
A.
Straelen
chosen
Straelen is a historic town in western Germany’s Lower Rhine region, known for its agricultural economy and proximity to the Dutch border.
-
B.
Steggerda
Steggerda is a small village in the municipality of Weststellingwerf in the province of Friesland in the northern Netherlands.
-
C.
Steenokkerzeel
Steenokkerzeel is a municipality in the Belgian province of Flemish Brabant, known for its proximity to Brussels and its location near major transport infrastructure.
-
D.
Tessenderlo
Tessenderlo is a municipality in the Belgian province of Limburg, known for its chemical industry and location near the Albert Canal.
-
E.
Zeveren
Zeveren is a village in East Flanders, Belgium, that forms part of the city of Deinze.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b0d5ec81908da8f38380dbdc7a |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.