Triple
T4549278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwabach |
E110122
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object | Schwabach River |
E370705
|
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: Schwabach River | Statement: [Schwabach, traversedBy, Schwabach River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwabach River Context triple: [Schwabach, traversedBy, Schwabach River]
-
A.
Schwabach River
chosen
The Schwabach River is a small river in Bavaria, Germany, that flows through the town of Schwabach before joining the Rednitz River.
-
B.
Lachen River
The Lachen River is a Himalayan mountain river in the Indian state of Sikkim, known for its glacial origins and role in feeding the Teesta River system.
-
C.
Schwalm River
The Schwalm River is a waterway in the German state of Hesse that lends its name to the surrounding Schwalm-Eder region.
-
D.
Würm River
The Würm River is a small river in Bavaria, Germany, known for flowing north from Lake Starnberg through towns such as Gauting and Starnberg before joining the Amper River.
-
E.
Schwabach
Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f3f8348190868e274ac4df87ce |
completed | March 20, 2026, 2:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf32f31ecc81909cb29b762481b08e |
completed | March 22, 2026, 12:08 a.m. |
Created at: March 20, 2026, 1:05 p.m.