Triple
T22084441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London River Services |
E545735
|
entity |
| Predicate | usesFareMedia |
P9955
|
FINISHED |
| Object | contactless payment cards |
—
|
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: contactless payment cards | Statement: [London River Services, usesFareMedia, contactless payment cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFareMedia Context triple: [London River Services, usesFareMedia, contactless payment cards]
-
A.
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.
-
B.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
-
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.
isWithinFareSystem
Indicates that one transportation service, route, or area operates under and is covered by a specified fare or ticketing system.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b95e908190bd846f531eb59b50 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.