Triple
T568129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop Fastpass |
E13600
|
entity |
| Predicate | supportsTapToPay |
P15672
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hop Fastpass, supportsTapToPay, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTapToPay Context triple: [Hop Fastpass, supportsTapToPay, true]
-
A.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
B.
paymentEnvironment
Indicates the context or setting in which a payment is initiated, processed, or completed (such as online, in-store, or in-app).
-
C.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
D.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
E.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with another entity.
- F. None of above. chosen
Provenance (4 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.