Triple
T25733660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wesel crossing |
E645312
|
entity |
| Predicate | usedRiver |
P83955
|
FINISHED |
| Object | Rhine |
—
|
NE NERFINISHED |
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: Rhine | Statement: [Wesel crossing, usedRiver, Rhine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRiver Context triple: [Wesel crossing, usedRiver, Rhine]
-
A.
usedWaterway
chosen
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
B.
hasRiverUse
Indicates that one entity makes use of a river associated with another entity, such as for transport, irrigation, recreation, or other purposes.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
riverMentioned
Indicates that a river is referenced or discussed in the given context or data.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbd5e2c819085a05ac41bd5b4a4 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 11:20 p.m.