Triple
T623754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemnitz River |
E14568
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Zwönitz |
E80007
|
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: Zwönitz | Statement: [Chemnitz River, hasTributary, Zwönitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zwönitz Context triple: [Chemnitz River, hasTributary, Zwönitz]
-
A.
Zwönitz
chosen
Zwönitz is a river in Saxony, Germany, that serves as one of the headstreams of the Chemnitz River.
-
B.
Pirna
Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
-
C.
Plauen
Plauen is a historic town in eastern Germany known for its textile industry and intricate lace production.
-
D.
Pöcking
Pöcking is a municipality in Bavaria, Germany, located on the western shore of Lake Starnberg and known for its affluent residential character.
-
E.
Ronsdorf
Ronsdorf is a district of the German city of Wuppertal in North Rhine-Westphalia, historically known as an independent town in the Bergisches Land region.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e41753881909f0faed720cc31bc |
completed | March 1, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a57b53ea008190be1a797f8d1d6c60 |
completed | March 2, 2026, 11:58 a.m. |
Created at: March 1, 2026, 7:35 p.m.