Triple
T1741483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clipper card |
E38241
|
entity |
| Predicate | supportsFareMedium |
P9955
|
FINISHED |
| Object | monthly passes |
—
|
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: monthly passes | Statement: [Clipper card, supportsFareMedium, monthly passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFareMedium Context triple: [Clipper card, supportsFareMedium, monthly passes]
-
A.
usesFareMedium
chosen
Indicates that an entity employs a particular fare medium (such as a ticket, card, or pass) as the method of payment or validation for a trip or service.
-
B.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
C.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
D.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
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 (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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.