Triple
T34740930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Drayton railway station |
E1001494
|
entity |
| Predicate | isServedByServiceType |
P849
|
FINISHED |
| Object | stopping services |
—
|
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: stopping services | Statement: [West Drayton railway station, isServedByServiceType, stopping services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServedByServiceType Context triple: [West Drayton railway station, isServedByServiceType, stopping services]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
C.
isServedByCode
Indicates that a service, resource, or item is provided, delivered, or fulfilled through a specific code.
-
D.
isServedByMode
Indicates that a service, route, or connection is provided or operated using a particular transportation mode.
-
E.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.