Triple
T596504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC 2.0 |
E17394
|
entity |
| Predicate | farePolicySupport |
P15903
|
FINISHED |
| Object | time-based passes |
—
|
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: time-based passes | Statement: [AFC 2.0, farePolicySupport, time-based passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: farePolicySupport Context triple: [AFC 2.0, farePolicySupport, time-based passes]
-
A.
fareFlexibility
Indicates how easily a fare can be changed, canceled, or refunded, and under what conditions or penalties.
-
B.
hasReservationPolicy
Indicates that an entity specifies or is governed by a particular policy regarding how reservations are made, managed, or honored.
-
C.
fareIntegration
Indicates that multiple transportation services or modes share a coordinated fare system, allowing passengers to use a single payment or ticket across them.
-
D.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
E.
fareProduct
Indicates a relationship where a specific fare or price offering is associated with a particular product or service option.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd3e5e08190be95cb2009aad42d |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cfb52c81908d816a4c5579c321 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985b7d7481909b5d30f4001ed61c |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.