Triple
T18702724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance & Leicester |
E457290
|
entity |
| Predicate | offeredInternetBanking |
P41922
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alliance & Leicester, offeredInternetBanking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredInternetBanking Context triple: [Alliance & Leicester, offeredInternetBanking, yes]
-
A.
offersOnlineBanking
chosen
Indicates that a financial institution provides banking services that customers can access and perform over the internet.
-
B.
hasBanking
Indicates that one entity provides or is associated with banking services or facilities for another entity.
-
C.
usesBanking
Indicates that one entity makes use of the banking services, facilities, or systems provided by another entity.
-
D.
servesBank
Indicates that one entity provides banking or financial services to another entity.
-
E.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56714d0588190ac050356bc2784fd |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.