Triple
T28470834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E720431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Synchronous Transport Signal level |
C54092
|
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: Synchronous Transport Signal level Context triple: [STS-1, instanceOf, Synchronous Transport Signal level]
-
A.
Ethernet synchronization standard
An Ethernet synchronization standard defines the methods and protocols that ensure precise, time-aligned data transmission across Ethernet networks for applications requiring accurate timing and frequency coordination.
-
B.
frequency synchronization equipment
Frequency synchronization equipment is a class of devices that generate, distribute, and align timing signals to ensure multiple systems or components operate at a common, stable frequency reference.
-
C.
IP video transport standard
An IP video transport standard defines the protocols, formats, and procedures for reliably transmitting, routing, and synchronizing video and associated data over IP-based networks.
-
D.
Fibre Channel protocol
Fibre Channel protocol is a high-speed network communication protocol primarily used to connect computer data storage to servers in storage area networks (SANs), providing reliable, lossless, and low-latency data transfer.
-
E.
time-sensitive networking specification
A time-sensitive networking specification defines standardized protocols and mechanisms that ensure deterministic, low-latency, and reliable data delivery over Ethernet-based networks for time-critical applications.
- F. None of above. chosen
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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:48 a.m.