Triple
T21568799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Anglia Great Northern |
E532229
|
entity |
| Predicate | railwaySector |
P68241
|
FINISHED |
| Object | passenger rail |
—
|
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: passenger rail | Statement: [West Anglia Great Northern, railwaySector, passenger rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwaySector Context triple: [West Anglia Great Northern, railwaySector, passenger rail]
-
A.
railwayNetworkSector
chosen
Indicates a relationship where something is classified as, or associated with, a specific sector or segment of a railway network.
-
B.
railwaySectorOrigin
Indicates the place or source from which a railway sector, line, or system originates or begins.
-
C.
railwayFocus
Indicates that something is a primary subject, theme, or point of attention specifically in the context of railways or railway-related matters.
-
D.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
E.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cad95c8190ab165ced6f242302 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.