Triple
T1066125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Euston – Birmingham |
E23213
|
entity |
| Predicate | lineSpeed |
P13562
|
FINISHED |
| Object | up to 125 mph |
—
|
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: up to 125 mph | Statement: [London Euston – Birmingham, lineSpeed, up to 125 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineSpeed Context triple: [London Euston – Birmingham, lineSpeed, up to 125 mph]
-
A.
originalLineSpeed
Indicates the speed at which something initially moves or operates before any changes or adjustments are made.
-
B.
writingSpeed
Indicates the rate at which an entity produces written content over a given period of time.
-
C.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
D.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
E.
speed
chosen
Indicates the rate at which an entity moves or changes position over 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.