Triple
T892868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Trust Bank |
E19278
|
entity |
| Predicate | hasBankingChannel |
P8080
|
FINISHED |
| Object | branch banking |
—
|
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: branch banking | Statement: [First Trust Bank, hasBankingChannel, branch banking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBankingChannel Context triple: [First Trust Bank, hasBankingChannel, branch banking]
-
A.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
B.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
-
C.
hasFederallyRecognizedBranch
Indicates that an entity possesses at least one branch, division, or subsidiary that is officially recognized by a federal authority.
-
D.
hasChannel
chosen
Indicates that one entity possesses, provides, or is associated with a particular communication or distribution channel.
-
E.
canUphold
Indicates that an entity has the ability or capacity to maintain, support, or sustain another entity, condition, or standard.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0304b081908d4c92bb2beadb81 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.