Triple
T28502200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zusam River |
E721262
|
entity |
| Predicate | riverSystemConnection |
P48420
|
FINISHED |
| Object | joins Danube via Wörnitz at Donauwörth |
—
|
LITERAL 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: joins Danube via Wörnitz at Donauwörth | Statement: [Zusam River, riverSystemConnection, joins Danube via Wörnitz at Donauwörth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverSystemConnection Context triple: [Zusam River, riverSystemConnection, joins Danube via Wörnitz at Donauwörth]
-
A.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
B.
waterwayLinkBetween
chosen
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
-
C.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
D.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- F. None of above.
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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 3:07 a.m.