Triple
T13784477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC single fare zone |
E331216
|
entity |
| Predicate | appliesToRiderCategory |
P15668
|
FINISHED |
| Object | adult riders |
—
|
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: adult riders | Statement: [TTC single fare zone, appliesToRiderCategory, adult riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRiderCategory Context triple: [TTC single fare zone, appliesToRiderCategory, adult riders]
-
A.
supportsRiderCategory
chosen
Indicates that one entity is capable of accommodating, enabling, or being compatible with a specified rider category.
-
B.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
C.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
D.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
-
E.
containsRideType
Indicates that one entity includes or offers a specific type or category of ride as part of its available options.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.