Triple
T17444856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QLine |
E424753
|
entity |
| Predicate | hasFareMedia |
P9955
|
FINISHED |
| Object | mobile ticketing |
—
|
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: mobile ticketing | Statement: [QLine, hasFareMedia, mobile ticketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareMedia Context triple: [QLine, hasFareMedia, mobile ticketing]
-
A.
isWithinFareSystem
Indicates that one transportation service, route, or area operates under and is covered by a specified fare or ticketing system.
-
B.
usesFareMedium
chosen
Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
-
C.
hasFarePaidArea
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
-
D.
hasNearbyPass
Indicates that an entity has at least one pass (e.g., transit or access pass) available within a short or locally defined distance from it.
-
E.
hasFareCardVendor
Indicates that an entity provides or is associated with a machine or service point where fare cards can be purchased, reloaded, or otherwise obtained.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffa2d84819086474649eba1065c |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.