Triple
T27660754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radius Bank |
E697113
|
entity |
| Predicate | hadRoutingNumber |
P111538
|
FINISHED |
| Object | 211371369 |
—
|
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: 211371369 | Statement: [Radius Bank, hadRoutingNumber, 211371369]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRoutingNumber Context triple: [Radius Bank, hadRoutingNumber, 211371369]
-
A.
hasRoutingNumberScope
Indicates that a routing number is valid or applicable only within a specified scope, such as a particular region, institution, or context.
-
B.
hadRoute
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
C.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
D.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
E.
hasBankCode
chosen
Indicates that an entity is associated with a specific bank identification code used to uniquely identify a bank or financial institution.
- 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.