Triple
T22236223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverlink County |
E549599
|
entity |
| Predicate | transferOfOperations |
P97562
|
FINISHED |
| Object | operations transferred to London Midland in 2007 |
—
|
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: operations transferred to London Midland in 2007 | Statement: [Silverlink County, transferOfOperations, operations transferred to London Midland in 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferOfOperations Context triple: [Silverlink County, transferOfOperations, operations transferred to London Midland in 2007]
-
A.
transferBetween
chosen
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
B.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
C.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
-
D.
transferComplex
Indicates the movement or relocation of a multi-component entity or system from one context, location, or state to another.
-
E.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf7b1d8819091087dcfdb2e967c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.