Triple
T22789122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScotRail West Lothian area |
E564059
|
entity |
| Predicate | fareTypeIncludes |
P8859
|
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: [ScotRail West Lothian area, fareTypeIncludes, single tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareTypeIncludes Context triple: [ScotRail West Lothian area, fareTypeIncludes, single tickets]
-
A.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
B.
fareTypes
chosen
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
-
C.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
-
D.
fareCollectionType
Indicates the method or system used to collect fares or payments for a service.
-
E.
partOfFareStructure
Indicates that one element is included as a component within a larger fare structure or pricing scheme.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c33be7c8190ad22391a85fa000d |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.