Triple
T30071248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British railway industry |
E764186
|
entity |
| Predicate | includesHighSpeedService |
P48478
|
FINISHED |
| Object | High Speed 1 |
—
|
NE NERFINISHED |
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: High Speed 1 | Statement: [British railway industry, includesHighSpeedService, High Speed 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHighSpeedService Context triple: [British railway industry, includesHighSpeedService, High Speed 1]
-
A.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
B.
hasHighSpeedLine
chosen
Indicates that there exists a high-speed rail line connection between the related entities.
-
C.
introducedAsHighSpeedService
Indicates that a service was launched or presented specifically as a high-speed offering.
-
D.
hasHighSpeedSections
Indicates that the entity includes segments or portions where operation or movement occurs at high speed.
-
E.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: April 29, 2026, 7 p.m.