Triple
T32941866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volga River at Tver |
E842690
|
entity |
| Predicate | hasBanksIn |
P142266
|
FINISHED |
| Object | central Tver |
—
|
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: central Tver | Statement: [Volga River at Tver, hasBanksIn, central Tver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBanksIn Context triple: [Volga River at Tver, hasBanksIn, central Tver]
-
A.
hasBankOn
chosen
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
B.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
C.
hasBanking
Indicates that one entity provides or is associated with banking services or facilities for another entity.
-
D.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
E.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:20 a.m.