Triple
T16471052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Railways Scottish Region |
E400059
|
entity |
| Predicate | usedTicketingSystem |
P61444
|
FINISHED |
| Object | British Rail national ticketing system |
—
|
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: British Rail national ticketing system | Statement: [British Railways Scottish Region, usedTicketingSystem, British Rail national ticketing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTicketingSystem Context triple: [British Railways Scottish Region, usedTicketingSystem, British Rail national ticketing system]
-
A.
primaryTicketingSystem
chosen
Indicates that one ticketing system is designated as the main or default system used for handling tickets in a given context.
-
B.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
C.
usedInE-tickets
Indicates that something (such as a method, technology, or feature) is employed or applied within the context of electronic tickets (e-tickets).
-
D.
usedForTicketType
Indicates that something is utilized or applicable for a specific type or category of ticket.
-
E.
ticketingSystemOperator
Indicates that one entity operates, manages, or administers the ticketing system used for issuing, tracking, or processing tickets for another entity or context.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.