Triple
T168839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MetroCard |
E3073
|
entity |
| Predicate | hasType |
P0
|
FINISHED |
| Object | Senior MetroCard |
E3073
|
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: Senior MetroCard | Statement: [MetroCard, hasType, Senior MetroCard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Senior MetroCard Context triple: [MetroCard, hasType, Senior MetroCard]
-
A.
MetroCard
chosen
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.
SmarTrip
SmarTrip is a rechargeable contactless smart card used to pay fares on the Washington, D.C. region’s public transit systems.
-
C.
SEPTA Key
SEPTA Key is a contactless smart fare card and payment system used across Philadelphia’s SEPTA public transit network.
-
D.
MetroAccess
MetroAccess is a paratransit service providing door-to-door transportation for people with disabilities in the Washington, D.C. metropolitan area.
-
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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258b6f4f88190b1264bbbeb19a29e |
completed | Feb. 28, 2026, 2:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2e0f8bf748190b2752f250a63d8e3 |
completed | Feb. 28, 2026, 12:35 p.m. |
Created at: Feb. 28, 2026, 2:34 a.m.