Triple
T7224437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham–Grantham line |
E150341
|
entity |
| Predicate | lineSpeedCategory |
P9902
|
FINISHED |
| Object | regional line |
—
|
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: regional line | Statement: [Nottingham–Grantham line, lineSpeedCategory, regional line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineSpeedCategory Context triple: [Nottingham–Grantham line, lineSpeedCategory, regional line]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
originalLineSpeed
Indicates the speed at which something initially moves or operates before any changes or adjustments are made.
-
C.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
D.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
E.
writingSpeed
Indicates the rate at which an entity produces written content over a given period of time.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9db51888190b8463d0003f334fa |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.