Triple
T28019967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola digital protocol |
E707658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | model railway digital control protocol |
C30219
|
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: model railway digital control protocol Context triple: [Motorola digital protocol, instanceOf, model railway digital control protocol]
-
A.
standardized rail interface
A standardized rail interface is a uniform physical and electrical connection system that allows different rail vehicles, components, or infrastructure elements to interoperate safely and efficiently across multiple networks or manufacturers.
-
B.
train control system
A train control system is a coordinated set of hardware and software components that monitor, regulate, and automate train movements to ensure safe, efficient, and reliable railway operations.
-
C.
railway signaling system
A railway signaling system is an integrated set of trackside and onboard equipment, rules, and communication protocols that control train movements to ensure safe separation, efficient routing, and protection against collisions.
-
D.
model railway scale
A model railway scale is a standardized ratio that defines the proportional size relationship between a miniature train layout and its real-world counterpart.
-
E.
railway communication system
chosen
A railway communication system is an integrated network of technologies and protocols that enable real-time exchange of information between trains, trackside equipment, and control centers to ensure safe, efficient, and coordinated railway operations.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:09 p.m.