Triple
T22203998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KeolisAmey Wales |
E548754
|
entity |
| Predicate | railServiceCategory |
P21523
|
FINISHED |
| Object | regional rail 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: regional rail services | Statement: [KeolisAmey Wales, railServiceCategory, regional rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railServiceCategory Context triple: [KeolisAmey Wales, railServiceCategory, regional rail services]
-
A.
railServiceType
chosen
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
B.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
C.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
D.
urbanRailCategory
Indicates the classification of an urban rail system according to its type or category (e.g., metro, tram, light rail).
-
E.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b25eac4819094b3c50027ed66db |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.