Triple
T11508884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Regional Card for All |
E272856
|
entity |
| Predicate | supportsDiscount |
P27915
|
FINISHED |
| Object | youth 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: youth fares | Statement: [One Regional Card for All, supportsDiscount, youth fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscount Context triple: [One Regional Card for All, supportsDiscount, youth fares]
-
A.
supportsAgeDiscounts
chosen
Indicates that the subject entity offers or honors special pricing or discounts based on a person's age.
-
B.
offersDiscountsOn
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
C.
discountRate
Indicates the percentage or amount by which a price, cost, or value is reduced relative to its original level.
-
D.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
E.
supportsBonus
Indicates that one entity provides or enables an additional benefit, reward, or bonus for 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db65eb081908613a1002c6a4fb4 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.