Triple
T8954789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anklam |
E213445
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Peene |
E372875
|
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: Peene | Statement: [Anklam, locatedOnRiver, Peene]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peene Context triple: [Anklam, locatedOnRiver, Peene]
-
A.
Peene River
chosen
The Peene River is a lowland river in northeastern Germany, often called the "Amazon of the North" for its largely untouched wetlands and rich biodiversity.
-
B.
Örtze River
The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
-
C.
Wakenitz
Wakenitz is a river in northern Germany that flows through the city of Lübeck and connects the Ratzeburger See to the Trave River.
-
D.
Rüdnitz
Rüdnitz is a small municipality in the Barnim district of the federal state of Brandenburg in northeastern Germany.
-
E.
Unstrut River
The Unstrut River is a tributary of the Saale in central Germany, flowing through Thuringia and Saxony-Anhalt and known for its scenic valleys, vineyards, and historic towns.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6724f3e4819092c6b13d80871e80 |
completed | April 1, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d28161b6ec8190ab91f7b00995e889 |
completed | April 5, 2026, 3:36 p.m. |
Created at: March 30, 2026, 7 p.m.