Triple
T16935529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA Zone 1 |
E410816
|
entity |
| Predicate | fareRevision |
P124810
|
FINISHED |
| Object | subject to periodic MBTA fare changes |
—
|
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: subject to periodic MBTA fare changes | Statement: [MBTA Zone 1, fareRevision, subject to periodic MBTA fare changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareRevision Context triple: [MBTA Zone 1, fareRevision, subject to periodic MBTA fare changes]
-
A.
fareIncreasesRequire
Indicates that any increase in fare is contingent upon or must be accompanied by a specified requirement or condition.
-
B.
fare
Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
-
C.
fareModel
Indicates a pricing relationship where a specific fare structure, rule set, or calculation method is applied to determine the cost of a trip or service.
-
D.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
E.
fareFlexibility
Indicates how easily a fare can be changed, canceled, or refunded, and under what conditions or penalties.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2a05f48190a0a8ac86985f4000 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.