Triple
T14302638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meppen |
E354605
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Lingen (Ems) |
E217689
|
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: Lingen (Ems) | Statement: [Meppen, nearbyCity, Lingen (Ems)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lingen (Ems) Context triple: [Meppen, nearbyCity, Lingen (Ems)]
-
A.
Lingen
chosen
Lingen is a town in Lower Saxony, Germany, known for its location on the River Ems and its role as a regional economic and cultural center.
-
B.
Bentheim
Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
-
C.
Himmerich
Himmerich is a hill in Germany’s Siebengebirge range, known for its forested slopes and hiking trails overlooking the Rhine valley.
-
D.
Gailingen
Gailingen is a village in the German municipality of Gailingen am Hochrhein in the state of Baden-Württemberg, near the Swiss border along the High Rhine.
-
E.
Dülmen
Dülmen is a town in western Germany’s North Rhine-Westphalia, known for its location between Münster and the Ruhr area and for the wild Dülmen ponies in the nearby nature reserve.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717fc2348190bb6ba3109bd2871f |
completed | April 14, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d2883e081909c53170ef30b4125 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:12 a.m.