Triple
T21014637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro (West Yorkshire) |
E517640
|
entity |
| Predicate | usesTicketingScheme |
P3383
|
FINISHED |
| Object | West Yorkshire multi-operator 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: West Yorkshire multi-operator tickets | Statement: [Metro (West Yorkshire), usesTicketingScheme, West Yorkshire multi-operator tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTicketingScheme Context triple: [Metro (West Yorkshire), usesTicketingScheme, West Yorkshire multi-operator tickets]
-
A.
hasTicketing
chosen
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
C.
usesTicketValidatorType
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
-
D.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5764188190829de6f5abd6e00f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.