Triple
T409585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransPennine Express |
E9459
|
entity |
| Predicate | franchiseType |
P9673
|
FINISHED |
| Object | rail franchise |
—
|
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: rail franchise | Statement: [TransPennine Express, franchiseType, rail franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseType Context triple: [TransPennine Express, franchiseType, rail franchise]
-
A.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
B.
controlsFranchiseType
Indicates that one entity has authority to determine or manage the type or category of franchise associated with another entity.
-
C.
franchiseLineage
Indicates the relationship by which one franchise is derived from, succeeds, or is otherwise historically connected to another within the same overarching series or brand.
-
D.
franchiseEventuallyBecame
Indicates that one franchise transformed into, was succeeded by, or ultimately came to be identified as another franchise over time.
-
E.
associatedFranchise
chosen
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.