Triple
T27660764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radius Bank |
E697113
|
entity |
| Predicate | hadSWIFTCode |
P111538
|
FINISHED |
| Object | RTNBUS33 |
—
|
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: RTNBUS33 | Statement: [Radius Bank, hadSWIFTCode, RTNBUS33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSWIFTCode Context triple: [Radius Bank, hadSWIFTCode, RTNBUS33]
-
A.
hasBankCode
chosen
Indicates that an entity is associated with a specific bank identification code used to uniquely identify a bank or financial institution.
-
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.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
D.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
E.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a016b08190973fd3a552a9757c |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:36 p.m.