Triple
T28012736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EasyGO electronic fare payment |
E707461
|
entity |
| Predicate | fareTypeSupported |
P8859
|
FINISHED |
| Object | concession fares |
—
|
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: concession fares | Statement: [EasyGO electronic fare payment, fareTypeSupported, concession fares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareTypeSupported Context triple: [EasyGO electronic fare payment, fareTypeSupported, concession fares]
-
A.
fareTypes
chosen
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
-
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.
fareSystemFeature
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
D.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
E.
farePolicySupport
Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:04 p.m.