Triple
T6782844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denton railway station |
E155725
|
entity |
| Predicate | ticketingPolicy |
P3383
|
FINISHED |
| Object | buy on train or in advance |
—
|
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: buy on train or in advance | Statement: [Denton railway station, ticketingPolicy, buy on train or in advance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketingPolicy Context triple: [Denton railway station, ticketingPolicy, buy on train or in advance]
-
A.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
B.
hasTicketing
chosen
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
C.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
D.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
E.
ticketingResponsibility
Indicates responsibility for issuing, managing, or handling tickets within a given context or system.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d289958481908ad4f9467a107083 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.