Triple
T37203021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumo (Class 803 variant) |
E922091
|
entity |
| Predicate | primaryRouteCorridor |
—
|
GENERATED |
| Object | London–Edinburgh |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRouteCorridor Context triple: [Lumo (Class 803 variant), primaryRouteCorridor, London–Edinburgh]
-
A.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
B.
primaryCorridorServed
chosen
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
C.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
D.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
E.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
- F. None of above.
Provenance (1 batch)
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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.