Triple
T15645319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EasyCard |
E376162
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | EasyCard Corporation |
E376162
|
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: EasyCard Corporation | Statement: [EasyCard, operator, EasyCard Corporation]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EasyCard Corporation Context triple: [EasyCard, operator, EasyCard Corporation]
-
A.
EasyCard
chosen
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.
-
B.
Metcard
Metcard was Melbourne’s former magnetic stripe ticketing system used for public transport before the introduction of the Myki smartcard.
-
C.
ConnectCard
ConnectCard is a reusable smart fare card used by Pittsburgh Regional Transit riders to pay for public transportation across the Pittsburgh area.
-
D.
EASY Card
The EASY Card is a contactless smart card used as a stored-value payment method for public transit services in the Miami-Dade area.
-
E.
Presto card
The Presto card is a reloadable smart card used for paying public transit fares across the Greater Toronto and Hamilton Area and other regions in Ontario, Canada.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed400ec8190a14a9f7cf3092865 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f4e558481909a39fdc5d104994a |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 10, 2026, 4:15 a.m.