Triple
T36628040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSS |
E904228
|
entity |
| Predicate | hasFareSystemAssociation |
P72429
|
FINISHED |
| Object | TTC fare system |
—
|
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: TTC fare system | Statement: [OSS, hasFareSystemAssociation, TTC fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareSystemAssociation Context triple: [OSS, hasFareSystemAssociation, TTC fare system]
-
A.
hasFareIntegration
Indicates that two or more transportation services or systems share a coordinated fare structure, allowing passengers to use a single ticket or payment arrangement across them.
-
B.
hasFareZoneSystem
chosen
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
C.
associatedWithTransitSystem
Indicates that an entity has a connection or involvement with a particular transit or transportation system.
-
D.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
E.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.