Triple
T10706959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digswell Viaduct |
E252432
|
entity |
| Predicate | railwayUsage |
P33182
|
FINISHED |
| Object | high-speed intercity services |
—
|
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: high-speed intercity services | Statement: [Digswell Viaduct, railwayUsage, high-speed intercity services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayUsage Context triple: [Digswell Viaduct, railwayUsage, high-speed intercity services]
-
A.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
B.
railwayLineUsage
chosen
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
C.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or period.
-
D.
railwayStationUsage
Indicates how frequently or extensively a railway station is used, such as by measuring passenger numbers, train traffic, or overall activity levels.
-
E.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddfbed48190810bb3faee473fde |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:12 p.m.