Triple
T10896433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransPennine North Route |
E257320
|
entity |
| Predicate | upgradeGoals |
P25631
|
FINISHED |
| Object | increased capacity |
—
|
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: increased capacity | Statement: [TransPennine North Route, upgradeGoals, increased capacity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradeGoals Context triple: [TransPennine North Route, upgradeGoals, increased capacity]
-
A.
upgradeGoal
chosen
Indicates that an entity has a target or intended improvement to a higher level, version, or state relative to its current condition.
-
B.
upgradeFocus
Indicates a shift of attention or priority from a lower level or version to a higher, improved, or more advanced one.
-
C.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
D.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
E.
upgradePath
Indicates the relationship by which one entity can be improved, enhanced, or transitioned into another, typically more advanced, version or state.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.