Triple
T10905592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrolink fare zones |
E257559
|
entity |
| Predicate | appliesToTicketMedium |
P92594
|
FINISHED |
| Object | paper tickets |
—
|
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: paper tickets | Statement: [Metrolink fare zones, appliesToTicketMedium, paper tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTicketMedium Context triple: [Metrolink fare zones, appliesToTicketMedium, paper tickets]
-
A.
usedForTicketType
chosen
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
B.
ticketMediumType
Indicates the type or format of the medium through which a ticket is issued, stored, or presented (e.g., paper, mobile, electronic).
-
C.
usesFareMedium
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.
-
D.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
E.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.