Triple
T32537409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1923 Grouping |
E831626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in railway history |
C24113
|
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: event in railway history Context triple: [1923 Grouping, instanceOf, event in railway history]
-
A.
railroad history event
chosen
A railroad history event is a significant occurrence or development in the evolution, operation, technology, policy, or cultural impact of rail transportation over time.
-
B.
railway history era
A railway history era is a distinct period characterized by specific technological, operational, and social developments in the evolution of rail transport.
-
C.
historical railway asset
A historical railway asset is any preserved or documented physical or digital artifact—such as tracks, rolling stock, stations, equipment, or records—associated with past railway operations and valued for its cultural, technological, or historical significance.
-
D.
historical railway interest
Historical railway interest is a fascination with the development, operation, and cultural impact of rail transport throughout history, often involving the study, preservation, and appreciation of trains, routes, infrastructure, and related artifacts.
-
E.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.