Triple
T11508997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FlexPass |
E272859
|
entity |
| Predicate | fareTechnology |
P395
|
FINISHED |
| Object | paper pass |
—
|
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: paper pass | Statement: [FlexPass, fareTechnology, paper pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareTechnology Context triple: [FlexPass, fareTechnology, paper pass]
-
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.
fareControlUnifiedWith
Indicates that separate fare control areas are combined into a single, shared fare-controlled zone.
-
C.
fareBrand
Indicates the specific fare category or brand under which a ticket or booking is sold, defining its associated rules, benefits, and restrictions.
-
D.
fareIntegrationScope
Indicates the extent to which fares are coordinated or unified across different transportation services or systems.
-
E.
fareSystem
chosen
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db65eb081908613a1002c6a4fb4 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.