Triple
T10857908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London public transport network |
E256316
|
entity |
| Predicate | contactlessPaymentIntroduced |
P15672
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [London public transport network, contactlessPaymentIntroduced, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactlessPaymentIntroduced Context triple: [London public transport network, contactlessPaymentIntroduced, 2014]
-
A.
supportsTapToPay
chosen
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
hasDigitalWallet
Indicates that an entity possesses or is associated with a digital wallet for storing and managing digital payment instruments or assets.
-
C.
hasNFC
Indicates that one entity possesses or supports Near Field Communication (NFC) capability in relation to another entity or context.
-
D.
cardAcceptance
Indicates that one party accepts or recognizes another party’s card as a valid form of payment or identification.
-
E.
compatibleICCardBrand
Indicates that one entity (such as a device or system) supports and can properly operate with IC cards of the specified brand.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.