Triple
T6159398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arriva Trains Northern |
E137402
|
entity |
| Predicate | railFranchiseSystem |
P53773
|
FINISHED |
| Object | British railway franchising system |
—
|
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: British railway franchising system | Statement: [Arriva Trains Northern, railFranchiseSystem, British railway franchising system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railFranchiseSystem Context triple: [Arriva Trains Northern, railFranchiseSystem, British railway franchising system]
-
A.
railFranchise
chosen
Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
E.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3445dc8190822954cee90f0dd7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.