Triple
T14917250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRR K2 |
E371411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pennsylvania Railroad locomotive class |
C3459
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Pennsylvania Railroad locomotive class Context triple: [PRR K2, instanceOf, Pennsylvania Railroad locomotive class]
-
A.
Southern Pacific Railroad steam locomotive class
A Southern Pacific Railroad steam locomotive class is a group of steam engines built or rostered by the Southern Pacific Railroad that share common design, performance, and operational characteristics for specific types of rail service.
-
B.
American locomotive
An American locomotive is a rail vehicle designed and built in the United States to provide motive power for trains, reflecting the country’s specific engineering practices, operating conditions, and historical development of rail transport.
-
C.
diesel-electric locomotive family
A diesel-electric locomotive family is a group of closely related locomotive models that share a common diesel engine and electric transmission design, with variations in power, configuration, and features tailored to different rail service needs.
-
D.
railway locomotive
chosen
A railway locomotive is a powered rail vehicle that provides the motive force to pull or push trains along railway tracks.
-
E.
electric locomotive class
An electric locomotive class is a category of railway locomotives designed and grouped by shared technical and performance characteristics, all powered by electricity from external sources such as overhead lines or third rails.
- F. None of above.
Provenance (1 batch)
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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:32 a.m.