Triple
T29141854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough 4, Düsseldorf |
E738656
|
entity |
| Predicate | sideOfRhine |
P106968
|
FINISHED |
| Object | left bank |
—
|
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: left bank | Statement: [Borough 4, Düsseldorf, sideOfRhine, left bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfRhine Context triple: [Borough 4, Düsseldorf, sideOfRhine, left bank]
-
A.
locatedOppositeAcrossRhineFrom
Indicates that one entity is situated on the other side of the Rhine River directly facing or across from the referenced entity.
-
B.
heightAboveRhine
Indicates the vertical elevation of an entity relative to the water level of the Rhine River.
-
C.
hasNeighbouringCountryAcrossRhine
Indicates that one country is geographically adjacent to another with the Rhine River forming or crossing their shared border.
-
D.
locatedOnRightBank
chosen
Indicates that one entity is situated on the right bank (right side) of a river or similar watercourse relative to its direction of flow.
-
E.
hasCityOnRightBank
Indicates that a city is located on the right bank of a specified river or watercourse.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6626fc3088190970ae48003cf2bf5 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:37 a.m.