Triple
T10443615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warszawska Karta Miejska |
E246229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport smart card |
C1449
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public transport smart card Context triple: [Warszawska Karta Miejska, instanceOf, public transport smart card]
-
A.
contactless smart card fare system
A contactless smart card fare system is an electronic payment and access control solution for public transportation that uses proximity cards or devices to automatically deduct fares and manage rider accounts when tapped on compatible readers.
-
B.
contact-type smart card
A contact-type smart card is a plastic card with an embedded integrated circuit chip that must physically connect to a reader via metallic contacts to securely store, process, and exchange data for applications like payments and identification.
-
C.
public transit fare card
chosen
A public transit fare card is a reusable, stored-value or pass-based card that riders use to pay for access to buses, trains, and other public transportation services.
-
D.
disposable smart card
A disposable smart card is a low-cost, single-use or limited-use card embedded with a microchip that securely stores and processes data for temporary transactions or access control before being discarded.
-
E.
fare card
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
- F. None of above.
Provenance (1 batch)
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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:15 p.m.