Triple
T8362386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta SkyMiles Blue American Express Card |
E197039
|
entity |
| Predicate | foreignTransactionFee |
P82297
|
FINISHED |
| Object | 0% |
—
|
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: 0% | Statement: [Delta SkyMiles Blue American Express Card, foreignTransactionFee, 0%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignTransactionFee Context triple: [Delta SkyMiles Blue American Express Card, foreignTransactionFee, 0%]
-
A.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
B.
fareSurchargeAppliesAt
Indicates that an additional fare or surcharge is in effect at a specified time, location, or under certain conditions.
-
C.
hasExchangeRateSpreadWith
Indicates a relationship where the difference (spread) between two entities’ exchange rates is defined or measured.
-
D.
foreignRecipient
Indicates that something is received by an entity located in or belonging to a different country or jurisdiction than the source.
-
E.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8074e4588190b394d1622adca2cb |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6 p.m.