Triple
T9690912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTP Autokey |
E234531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Network Time Protocol extension |
C844
|
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: Network Time Protocol extension Context triple: [NTP Autokey, instanceOf, Network Time Protocol extension]
-
A.
time synchronization protocol
chosen
A time synchronization protocol is a set of rules and mechanisms that enable multiple systems or devices in a network to coordinate and maintain a consistent, accurate notion of time.
-
B.
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.
-
C.
TLS extension
A TLS extension is an optional, standardized addition to the TLS protocol that allows clients and servers to negotiate extra capabilities or parameters (such as supported protocols, server names, or security features) during the handshake.
-
D.
IPsec extension
An IPsec extension is a conceptual class that augments core IPsec functionality with additional security, configuration, or protocol features to support enhanced or specialized network protection requirements.
-
E.
NAT traversal framework
A NAT traversal framework is a software system that provides reusable mechanisms and protocols to enable networked applications to establish and maintain connections across Network Address Translation (NAT) boundaries.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.