Triple
T543575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube |
E12683
|
entity |
| Predicate | sourceConfluenceLocation |
P3421
|
FINISHED |
| Object | near Donaueschingen |
—
|
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: near Donaueschingen | Statement: [Danube, sourceConfluenceLocation, near Donaueschingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceConfluenceLocation Context triple: [Danube, sourceConfluenceLocation, near Donaueschingen]
-
A.
confluenceLocation
chosen
Indicates the place where two or more flowing entities (such as rivers or streams) meet and merge.
-
B.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
confluenceWith
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
D.
confluenceRegion
Indicates the region where two or more entities (typically flows, paths, or streams) merge or come together into a single combined course.
-
E.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498dea88881908a938fe8f2313bec |
completed | March 1, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.