Triple
T10231710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FNBO Direct |
E243354
|
entity |
| Predicate | bankType |
P33501
|
FINISHED |
| Object | direct bank |
—
|
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: direct bank | Statement: [FNBO Direct, bankType, direct bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bankType Context triple: [FNBO Direct, bankType, direct bank]
-
A.
hasBankType
chosen
Indicates that an entity is associated with or classified by a particular type or category of bank.
-
B.
bank
Indicates that an entity provides financial services such as holding deposits, lending money, or managing financial transactions for another entity.
-
C.
banksOften
Indicates that the subject frequently or habitually engages in banking activities with the object (such as depositing, withdrawing, or otherwise using banking services).
-
D.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:20 a.m.