Triple
T24534350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merseytravel zone E |
E606903
|
entity |
| Predicate | hasTicketTypeCoverage |
P132047
|
FINISHED |
| Object | single 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: single tickets | Statement: [Merseytravel zone E, hasTicketTypeCoverage, single tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketTypeCoverage Context triple: [Merseytravel zone E, hasTicketTypeCoverage, single tickets]
-
A.
hasTicketCategory
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
B.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
C.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
D.
hasTicketOption
chosen
Indicates that an entity offers or is associated with a particular ticket choice or type as an available option.
-
E.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.