Triple
T14125746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wupper basin |
E340025
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Morsbach |
E948661
|
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: Morsbach | Statement: [Wupper basin, hasTributary, Morsbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morsbach Context triple: [Wupper basin, hasTributary, Morsbach]
-
A.
Morsbach
chosen
Morsbach is a small river in North Rhine-Westphalia, Germany, that flows through the city of Remscheid.
-
B.
Botenheim
Botenheim is a small village and district (Ortsteil) of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
-
C.
Burbach
Burbach is a district of the city of Saarbrücken in the German federal state of Saarland.
-
D.
Beutelsbach
Beutelsbach is a small municipality in the rural Passau district of Lower Bavaria in southeastern Germany.
-
E.
Morbach
Morbach is a small town in the Hunsrück region of Rhineland-Palatinate in western Germany, known for its scenic forests and rural landscapes.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd54fc136881908f0ff5cafa604811 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 9, 2026, 10:22 p.m.