Triple
T21568766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Anglia Great Northern |
E532229
|
entity |
| Predicate | operatedRouteGroup |
P84215
|
FINISHED |
| Object | West Anglia routes |
—
|
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: West Anglia routes | Statement: [West Anglia Great Northern, operatedRouteGroup, West Anglia routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRouteGroup Context triple: [West Anglia Great Northern, operatedRouteGroup, West Anglia routes]
-
A.
operatedRoute
Indicates that a transportation service or carrier runs or manages a specific route.
-
B.
routeGroup
Indicates that multiple routes are grouped together as a single logical or organizational unit.
-
C.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
-
D.
routeArea
Indicates that an area is associated with, covered by, or traversed by a particular route.
-
E.
routeOperator
chosen
Indicates that an agent operates, manages, or is responsible for running a particular route or service path.
- 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.