Triple
T22135391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knutsford railway station |
E547011
|
entity |
| Predicate | servedByRegionalServices |
P99269
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Knutsford railway station, servedByRegionalServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByRegionalServices Context triple: [Knutsford railway station, servedByRegionalServices, yes]
-
A.
hasRegionalServices
chosen
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
-
B.
regionalServiceOperational
Indicates that a service is currently functioning and available within a specified geographic region.
-
C.
isRegionalServiceCentre
Indicates that an entity functions as a regional service center responsible for providing services or support to a defined geographic area.
-
D.
isInhabitedRegionServed
Indicates that a particular inhabited region is provided with services or coverage by a specified entity (such as an organization, facility, or infrastructure).
-
E.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b9ee54819081141c4f28e1211a |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.