Triple
T34888448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Zone 8 |
E1006213
|
entity |
| Predicate | hasDiscountPolicy |
P132445
|
FINISHED |
| Object | promotional fares |
—
|
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: promotional fares | Statement: [Amtrak Zone 8, hasDiscountPolicy, promotional fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscountPolicy Context triple: [Amtrak Zone 8, hasDiscountPolicy, promotional fares]
-
A.
supportsDiscounts
chosen
Indicates that an entity provides or is compatible with special price reductions or promotional discounts.
-
B.
usesDiscountFactor
Indicates that an entity applies a discount factor when evaluating or calculating the value of something over time or across scenarios.
-
C.
hasCouponRate
Indicates the interest rate or periodic interest payment percentage associated with a bond or similar fixed-income instrument.
-
D.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
-
E.
discountMechanism
Indicates a relationship where one entity defines the method, rule, or process by which a discount is calculated, applied, or granted to 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4 p.m.