Triple
T13295482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zones 1–5 |
E316668
|
entity |
| Predicate | definesPriceFor |
P109390
|
FINISHED |
| Object | season tickets |
—
|
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: season tickets | Statement: [Travelcard Zones 1–5, definesPriceFor, season tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPriceFor Context triple: [Travelcard Zones 1–5, definesPriceFor, season tickets]
-
A.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
B.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
C.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
D.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
E.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:28 p.m.