Triple
T15241790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson (CTA Red Line station) |
E364272
|
entity |
| Predicate | farePaidTransferAvailable |
P19480
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Jackson (CTA Red Line station), farePaidTransferAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePaidTransferAvailable Context triple: [Jackson (CTA Red Line station), farePaidTransferAvailable, yes]
-
A.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
-
B.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
C.
fareContext
Indicates the pricing or fare-related conditions under which a transaction, service, or travel arrangement is applied.
-
D.
hasFreeTransfer
chosen
Indicates that one entity allows or provides a transfer to another service, route, or segment without additional cost.
-
E.
hasFarePaidArea
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.