Triple
T5634809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fyris River |
E147920
|
entity |
| Predicate | hasBankFeature |
P1010
|
FINISHED |
| Object | parks in Uppsala |
—
|
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: parks in Uppsala | Statement: [Fyris River, hasBankFeature, parks in Uppsala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBankFeature Context triple: [Fyris River, hasBankFeature, parks in Uppsala]
-
A.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
B.
hasBank
chosen
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
C.
hasFeatureOnBanknotes
Indicates that a particular feature, such as a design element or security mark, appears on one or more banknotes.
-
D.
hasBankingInTurns
Indicates that an entity participates in banking activities that occur in discrete, alternating turns rather than continuously.
-
E.
hasATMNetwork
Indicates that an entity operates, participates in, or is connected to a particular automated teller machine (ATM) network for financial transactions.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226118548190877793dadf6cacba |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.