Triple
T37417880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metra fare zones |
E929765
|
entity |
| Predicate | pricingMethod |
P8244
|
FINISHED |
| Object | zone-to-zone fare table |
—
|
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: zone-to-zone fare table | Statement: [Metra fare zones, pricingMethod, zone-to-zone fare table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pricingMethod Context triple: [Metra fare zones, pricingMethod, zone-to-zone fare table]
-
A.
usesPricingMethod
Indicates that one entity applies or relies on a particular pricing method to determine prices or costs.
-
B.
pricingStrategy
chosen
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
C.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
D.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
E.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.