Triple
T1002852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanover |
E21642
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Leine River |
E35561
|
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: Leine River | Statement: [Hanover, locatedOnRiver, Leine River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leine River Context triple: [Hanover, locatedOnRiver, Leine River]
-
A.
Leine
chosen
The Leine is a major river in central Germany that flows through the federal state of Lower Saxony, passing cities such as Göttingen and Hanover before joining the Aller.
-
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.
Lippe
Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
-
D.
Inn River
The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
-
E.
Rhens
Rhens is a historic town on the Rhine River in western Germany, known for its medieval role as a meeting place of the prince-electors of the Holy Roman Empire.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fe0a548190aee8abf1890e141e |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad1c8c828481909013039009446dc0 |
completed | March 8, 2026, 6:51 a.m. |
Created at: March 1, 2026, 7:41 p.m.