Triple
T9901584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unterweser |
E182294
|
entity |
| Predicate | isSectionOf |
P3120
|
FINISHED |
| Object | lower Weser |
E33257
|
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: lower Weser | Statement: [Unterweser, isSectionOf, lower Weser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: lower Weser Context triple: [Unterweser, isSectionOf, lower Weser]
-
A.
Lippe
Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
-
B.
Lippe
The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
-
C.
Wupper
The Wupper is a river in North Rhine-Westphalia, Germany, known for flowing through the industrial city of Wuppertal and its surrounding region.
-
D.
Weser
chosen
The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
-
E.
Wupper basin
The Wupper basin is a river catchment area in North Rhine-Westphalia, Germany, drained by the Wupper River and encompassing several towns and cities in the Bergisches Land region.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e221448190b536742d1269f9d7 |
completed | April 2, 2026, 12:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb2125208190b4cf549d67d1ca42 |
completed | April 5, 2026, 4:54 a.m. |
Created at: March 30, 2026, 8:40 p.m.