Triple
T2033492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möhne Dam |
E44569
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Soest |
E175283
|
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: Soest | Statement: [Möhne Dam, locatedNear, Soest]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soest Context triple: [Möhne Dam, locatedNear, Soest]
-
A.
Soest
chosen
Soest is a historic town in North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and former significance as a Hanseatic trading center.
-
B.
Delmenhorst
Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of Lower Saxony.
-
C.
Wassenaar
Wassenaar is an affluent coastal town in the western Netherlands known for its wooded estates, beaches, and role as a residential area for diplomats and expatriates.
-
D.
Lüneburg
Lüneburg is a historic Hanseatic town in northern Germany renowned for its medieval architecture and former wealth from salt mining.
-
E.
Aurich
Aurich is a historic town in northwestern Germany that serves as one of the principal urban centers of the East Frisia region in Lower Saxony.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5d85c2208190bbd612a3ecbbacfd |
completed | March 9, 2026, 5:41 a.m. |
Created at: March 4, 2026, 7:39 p.m.