Triple
T38160961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco Docklands |
E953016
|
entity |
| Predicate | usedFareSystem |
P395
|
FINISHED |
| Object | integrated London 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: integrated London fare system | Statement: [Serco Docklands, usedFareSystem, integrated London fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFareSystem Context triple: [Serco Docklands, usedFareSystem, integrated London fare system]
-
A.
fareSystemUse
Indicates the use or application of a particular fare system for travel, ticketing, or pricing.
-
B.
fareSystemPreviously
Indicates that a particular fare system existed or was in use at an earlier time relative to another fare system or time period.
-
C.
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.
-
D.
fareSystem
chosen
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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.