Triple
T9136371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wise |
E219214
|
entity |
| Predicate | offersLowerFeesComparedTo |
P16098
|
FINISHED |
| Object | traditional banks |
—
|
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: traditional banks | Statement: [Wise, offersLowerFeesComparedTo, traditional banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersLowerFeesComparedTo Context triple: [Wise, offersLowerFeesComparedTo, traditional banks]
-
A.
reducedCommissionRate
Indicates that the commission rate applied to a transaction or agreement is lower than the standard or previously agreed rate.
-
B.
comparedToOtherFares
Indicates a comparison relationship between one fare and other available fares, typically in terms of price, conditions, or benefits.
-
C.
transactionFees
Indicates the fees charged or incurred as part of executing a financial transaction between parties.
-
D.
priceRelationship
chosen
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
E.
hasLowerMonthlyPaymentThan
Indicates that one entity’s required monthly payment amount is less than that of 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8df68108190bb2df0583c5ad481 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.