Triple
T9105261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Yorkshire Metro |
E218461
|
entity |
| Predicate | ticketProduct |
P36295
|
FINISHED |
| Object | multi-operator bus 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: multi-operator bus tickets | Statement: [West Yorkshire Metro, ticketProduct, multi-operator bus tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketProduct Context triple: [West Yorkshire Metro, ticketProduct, multi-operator bus tickets]
-
A.
ticketingProduct
chosen
Indicates a relationship where an entity is associated with, or offered as, a ticketing-related product (such as a service or item used for issuing, managing, or selling tickets).
-
B.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
C.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
D.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
E.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca5714d048190a633caaaa707ac3b |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.