Triple
T1645069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leine |
E35561
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Leine (German) |
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 (German) | Statement: [Leine, hasNameInLanguage, Leine (German)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leine (German) Context triple: [Leine, hasNameInLanguage, Leine (German)]
-
A.
Old Rhine
The Old Rhine is a historic branch of the Rhine River in the western Netherlands that flows through cities such as Leiden before reaching the North Sea.
-
B.
Untere Aller
Untere Aller is the lower course of the Aller River in northern Germany, known for its floodplains, wetlands, and ecological significance.
-
C.
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.
-
D.
Lippe
Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
-
E.
Lippe
The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a41e5a08190b97dd1c0b12c662a |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad60a26350819087e7a87b52561143 |
completed | March 8, 2026, 11:42 a.m. |
Created at: March 4, 2026, 7:28 p.m.