Triple
T1384580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMNY |
E29814
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | OMNY cards |
E29814
|
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: OMNY cards | Statement: [OMNY, hasComponent, OMNY cards]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OMNY cards Context triple: [OMNY, hasComponent, OMNY cards]
-
A.
MetroCard
MetroCard is a magnetic stripe payment card formerly used as the primary method for paying fares on New York City’s public transit system, including subways and buses.
-
B.
OMNY
chosen
OMNY is the contactless fare payment system used by New York City's public transit network, replacing the MetroCard with tap-and-go payments via cards, phones, and wearables.
-
C.
SmarTrip
SmarTrip is a rechargeable contactless smart card used to pay fares on the Washington, D.C. region’s public transit systems.
-
D.
Opal card
The Opal card is a reusable, contactless smartcard used to pay for public transport across much of New South Wales, Australia.
-
E.
MBTA CharlieCard
The MBTA CharlieCard is a reusable contactless smart card used to pay fares on Boston’s public transit system, including subways, buses, and some commuter rail and ferry services.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33896548190b44f70c9aaaed9b6 |
completed | March 1, 2026, 10:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acde1f08e08190871fd9d539e902c8 |
completed | March 8, 2026, 2:25 a.m. |
Created at: March 1, 2026, 7:59 p.m.