Triple
T10032573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST Express bus |
E204884
|
entity |
| Predicate | fareSystem |
P395
|
FINISHED |
| Object | ORCA card |
E52122
|
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: ORCA card | Statement: [ST Express bus, fareSystem, ORCA card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ORCA card Context triple: [ST Express bus, fareSystem, ORCA card]
-
A.
ORCA card
chosen
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.
-
B.
Opal card
The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
-
C.
TransLink card
The TransLink card was a contactless smart card used for fare payment on public transit systems in the San Francisco Bay Area before being succeeded by the Clipper card.
-
D.
Oyster card
The Oyster card is a rechargeable smartcard used for convenient, cashless payment on public transport services across London.
-
E.
TAP card
The TAP card is a reusable contactless smart card used to pay fares across public transit systems in the Los Angeles County region.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce47845c8190ab5696267fdedcad |
completed | April 2, 2026, 2:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b60256b48190829cfdbff0105cc0 |
completed | April 5, 2026, 7:20 p.m. |
Created at: March 30, 2026, 8:54 p.m.