Triple
T36280086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Manchester rail zone |
E892915
|
entity |
| Predicate | usedByTicketType |
P92594
|
FINISHED |
| Object | season 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: season tickets | Statement: [Greater Manchester rail zone, usedByTicketType, season tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTicketType Context triple: [Greater Manchester rail zone, usedByTicketType, season tickets]
-
A.
usedForTicketType
chosen
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
B.
usedByTicket
Indicates that something (such as a resource, item, or service) is utilized or referenced by a specific ticket.
-
C.
usesTicketValidatorType
Indicates that an entity employs or is associated with a specific type or category of ticket validation device or method.
-
D.
usesTicketZone
Indicates that an entity’s validity, access, or operation is determined by or restricted to a specific ticket zone.
-
E.
companionTicketType
Indicates the type or category of ticket that is associated with or issued to a companion of a primary ticket holder.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.