Triple
T31061298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q44 Select Bus Service |
E791546
|
entity |
| Predicate | usesFareCollection |
P112377
|
FINISHED |
| Object | off-board fare collection |
—
|
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: off-board fare collection | Statement: [Q44 Select Bus Service, usesFareCollection, off-board fare collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFareCollection Context triple: [Q44 Select Bus Service, usesFareCollection, off-board fare collection]
-
A.
hasAutomaticFareCollection
Indicates that an entity is equipped with a system that automatically collects fares or payments from users without manual processing.
-
B.
usesFareMedium
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.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
-
D.
fareSystemFeature
chosen
Indicates that a fare system possesses or supports a particular feature, function, or characteristic related to how fares are calculated, managed, or used.
-
E.
fareSystem
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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:01 p.m.