Triple
T34888426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Zone 8 |
E1006213
|
entity |
| Predicate | hasFareRule |
P195469
|
FINISHED |
| Object | zone-based pricing differentials |
—
|
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-based pricing differentials | Statement: [Amtrak Zone 8, hasFareRule, zone-based pricing differentials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareRule Context triple: [Amtrak Zone 8, hasFareRule, zone-based pricing differentials]
-
A.
hasFareIntegration
Indicates that two or more transportation services or systems share a coordinated fare structure, allowing passengers to use a single ticket or payment arrangement across them.
-
B.
hasFareBoundary
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
C.
fareAppliesTo
Indicates that a specific fare is applicable to a particular trip, service, passenger category, or travel condition.
-
D.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
E.
hasFareZoneCode
Indicates that an entity is associated with a specific fare zone identifier used for pricing or tariff purposes.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4 p.m.