Triple
T8341582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberweser |
E195927
|
entity |
| Predicate | hasGermanName |
P1435
|
FINISHED |
| Object | Oberweser |
E195927
|
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: Oberweser | Statement: [Oberweser, hasGermanName, Oberweser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberweser Context triple: [Oberweser, hasGermanName, Oberweser]
-
A.
Oberweser
chosen
Oberweser is the name given to the upper course of the Weser River in central Germany, encompassing its initial stretch after the confluence of its headstreams.
-
B.
Eschwege
Eschwege is a small historic town in the German state of Hesse, known for its medieval architecture and location near the Werra River.
-
C.
Niederwiesa
Niederwiesa is a municipality in the Free State of Saxony in eastern Germany, situated near the city of Chemnitz.
-
D.
Oderberg
Oderberg is a small historic town in northeastern Germany near the Oder River, known for its scenic natural surroundings and proximity to the Polish border.
-
E.
Eckersbach
Eckersbach is a district of the city of Zwickau in the German state of Saxony, known primarily as a residential area.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe9efec81908e0c9ded3963bac5 |
completed | March 31, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc72bc43c81909d95c7eb6aefc403 |
completed | April 2, 2026, 1:32 a.m. |
Created at: March 30, 2026, 5:58 p.m.