Triple
T1558216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weser |
E33257
|
entity |
| Predicate | passesThroughCity |
P416
|
FINISHED |
| Object | Hameln |
E178114
|
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: Hameln | Statement: [Weser, passesThroughCity, Hameln]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hameln Context triple: [Weser, passesThroughCity, Hameln]
-
A.
Hameln
chosen
Hameln is a historic town in Lower Saxony, Germany, best known as the setting of the Pied Piper of Hamelin legend.
-
B.
Hildesheim
Hildesheim is a historic city in northern Germany renowned for its medieval architecture and UNESCO-listed Romanesque churches.
-
C.
Wolfenbüttel
Wolfenbüttel is a historic town in Lower Saxony, Germany, known for its Renaissance castle and rich cultural heritage.
-
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.
Delmenhorst
Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9088355048190adad5ea2bb558d13 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad68079e448190b71c2cd194abeb86 |
completed | March 8, 2026, 12:13 p.m. |
Created at: March 4, 2026, 7:27 p.m.