Triple
T1791781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travel Wallet |
E39511
|
entity |
| Predicate | fareDeductionMethod |
P15667
|
FINISHED |
| Object | deducts fare amount per trip |
—
|
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: deducts fare amount per trip | Statement: [Travel Wallet, fareDeductionMethod, deducts fare amount per trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareDeductionMethod Context triple: [Travel Wallet, fareDeductionMethod, deducts fare amount per trip]
-
A.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
B.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
C.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
D.
fareCapping
chosen
Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
-
E.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.