Triple
T15245257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston Loop Line |
E364361
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | Oyster card |
E60075
|
NE 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: Oyster card | Statement: [Kingston Loop Line, fareSystem, Oyster card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oyster card Context triple: [Kingston Loop Line, fareSystem, Oyster card]
-
A.
Oyster card
chosen
The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
-
B.
Octopus card
The Octopus card is a rechargeable contactless smart card widely used in Hong Kong for public transport fares and everyday electronic payments.
-
C.
ORCA card
The ORCA card is a reusable, contactless smart card used to pay fares across multiple public transit systems in the Puget Sound region of Washington State.
-
D.
Merseytravel smartcard
The Merseytravel smartcard is a contactless travel card used for seamless payment and ticketing across public transport services in the Merseyside region of England.
-
E.
System One travelcards
System One travelcards are integrated public transport tickets in Greater Manchester that allow unlimited travel across multiple operators and modes within selected zones.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f306f08190be448b215d6c9b6c |
completed | April 15, 2026, 9:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd461cf08190a506aac2f0cec83a |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:13 a.m.