Triple
T892867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Trust Bank |
E19278
|
entity |
| Predicate | typeOfBanknotesIssued |
P6036
|
FINISHED |
| Object | sterling banknotes |
—
|
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: sterling banknotes | Statement: [First Trust Bank, typeOfBanknotesIssued, sterling banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBanknotesIssued Context triple: [First Trust Bank, typeOfBanknotesIssued, sterling banknotes]
-
A.
typeOfBanknotes
chosen
Indicates a relationship where one entity specifies the kind or category of banknotes associated with another entity.
-
B.
banknoteDenomination
Indicates the specific face value assigned to a banknote in a given currency.
-
C.
currentBanknoteSeries
Indicates that the subject is part of, or associated with, the banknote series that is currently in official circulation.
-
D.
frequentlyUsedBanknotes
Indicates that the referenced banknotes are commonly or regularly used in transactions within a given context or system.
-
E.
hasBanknotesIssuedBy
Indicates that one entity possesses or contains banknotes that were issued by another entity.
- 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.