Triple
T13458523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASY Card |
E311296
|
entity |
| Predicate | brandName |
P1500
|
FINISHED |
| Object | EASY Card |
E311296
|
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: EASY Card | Statement: [EASY Card, brandName, EASY Card]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EASY Card Context triple: [EASY Card, brandName, EASY Card]
-
A.
EASY Card
chosen
The EASY Card is a contactless smart card used as a stored-value payment method for public transit services in the Miami-Dade area.
-
B.
EasyCard
EasyCard is a rechargeable contactless smart card widely used in Taipei and other parts of Taiwan for public transportation fares and small-value retail payments.
-
C.
Breeze Card
The Breeze Card is a reusable smart fare card used for paying transit fares across the Metropolitan Atlanta Rapid Transit Authority (MARTA) system in Atlanta, Georgia.
-
D.
Leap Card
Leap Card is a reusable, contactless smart card used for paying public transport fares across Dublin and other parts of Ireland.
-
E.
Pronto card
The Pronto card is a reloadable smart fare card used for paying public transit fares across the San Diego Metropolitan Transit System and related 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0a75008190a508060c85f73604 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f739a001d08190ae5664c6670540e7 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:41 p.m.