Triple
T11909442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 5 |
E283354
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Oyster card system |
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 system | Statement: [Zone 5, usedBy, Oyster card system]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oyster card system Context triple: [Zone 5, usedBy, Oyster card system]
-
A.
Oyster card
chosen
The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
-
B.
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.
-
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.
Metro TAP card
The Metro TAP card is a reusable, reloadable smart fare card used for contactless payment across the Los Angeles County public transit system.
-
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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f44004b454819091b41bac99895106 |
completed | May 1, 2026, 5:54 a.m. |
Created at: April 8, 2026, 9:44 p.m.