Triple
T15947548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naab River |
E386722
|
entity |
| Predicate | hasLeftTributary |
P415
|
FINISHED |
| Object | Schwarzach (Naab) |
E883248
|
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: Schwarzach (Naab) | Statement: [Naab River, hasLeftTributary, Schwarzach (Naab)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwarzach (Naab) Context triple: [Naab River, hasLeftTributary, Schwarzach (Naab)]
-
A.
Schwarzach am Main
Schwarzach am Main is a small municipality in the Lower Franconia region of Bavaria, Germany, situated along the Main River and known for its winegrowing and historic monastery.
-
B.
Schwarzach
chosen
Schwarzach is a municipality in the Straubing-Bogen district of Lower Bavaria, Germany, known for its rural setting in the Bavarian Forest region.
-
C.
Schwarzach
Schwarzach is a river in Bavaria, Germany, known as a tributary of the Rednitz.
-
D.
Schwarzach
Schwarzach is a municipality in the Austrian state of Vorarlberg, located in the district of Bregenz.
-
E.
Schwarzach (Rezat)
Schwarzach (Rezat) is a river in Bavaria, Germany, that serves as one of the headstreams forming the Rednitz River.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d2fda8819085279d2a0f8a02ab |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5c0c8a481908aa7a40bca15e38e |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:53 a.m.