Triple
T9767768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamyshin |
E237038
|
entity |
| Predicate | hasRiverBankLocation |
P39043
|
FINISHED |
| Object | right bank of the Volga River |
—
|
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: right bank of the Volga River | Statement: [Kamyshin, hasRiverBankLocation, right bank of the Volga River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverBankLocation Context triple: [Kamyshin, hasRiverBankLocation, right bank of the Volga River]
-
A.
locatedOnBankOfRiver
chosen
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
B.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
C.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
-
D.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
E.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.