Triple
T18800538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 One Zone-IA |
E459744
|
entity |
| Predicate | retrievalFee |
P133067
|
FINISHED |
| Object | per-GB retrieval fee applies |
—
|
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: per-GB retrieval fee applies | Statement: [S3 One Zone-IA, retrievalFee, per-GB retrieval fee applies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retrievalFee Context triple: [S3 One Zone-IA, retrievalFee, per-GB retrieval fee applies]
-
A.
transactionFees
Indicates the fees charged or incurred as part of executing a financial transaction between parties.
-
B.
subsequentFees
Indicates that additional fees are charged or become applicable after an initial fee or primary transaction has occurred.
-
C.
foreignTransactionFee
Indicates that a fee is charged for processing a transaction involving a foreign currency or occurring outside the cardholder’s home country.
-
D.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
E.
fundingCost
Indicates the financial expense or resources required to provide funding for an entity, project, or activity.
- F. None of above. chosen
Provenance (4 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02332d88190b68feea7f2f86d06 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.