Triple
T32547690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrebus Roma |
E831888
|
entity |
| Predicate | supportsContactlessCard |
—
|
GENERATED |
| Object | Metrebus card |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContactlessCard Context triple: [Metrebus Roma, supportsContactlessCard, Metrebus card]
-
A.
supportsTapToPay
chosen
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
supportsCardlessIdentification
Indicates that an entity enables identification or authentication of a person without requiring a physical card.
-
C.
supportsCardRegistration
Indicates that an entity provides the capability to register a payment or identification card for use within a system or service.
-
D.
supportsSmartcards
Indicates that one entity provides compatibility with or the ability to use smartcard-based functionality for another entity.
-
E.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.