Triple
T34154599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Vancouver public transit network |
E876098
|
entity |
| Predicate | usesPaymentTechnology |
P21821
|
FINISHED |
| Object | contactless smart card |
—
|
LITERAL 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: contactless smart card | Statement: [Metro Vancouver public transit network, usesPaymentTechnology, contactless smart card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPaymentTechnology Context triple: [Metro Vancouver public transit network, usesPaymentTechnology, contactless smart card]
-
A.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
paymentNetworkType
Indicates the type or category of payment network through which a payment is processed or routed.
-
C.
paymentNetworkScope
Indicates the extent or domain within which a payment network operates or is considered applicable in the relationship.
-
D.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
-
E.
paymentSystem
chosen
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
- F. None of above.
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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:54 a.m.