Triple
T35516285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JREAP |
E1026427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical data link extension protocol |
C7819
|
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: tactical data link extension protocol Context triple: [JREAP, instanceOf, tactical data link extension protocol]
-
A.
Protocol Data Unit
A Protocol Data Unit is a formatted block of data, including control information and user data, exchanged between peer entities at a specific layer of a network protocol stack.
-
B.
avionics data bus
An avionics data bus is a communication system within an aircraft that transfers digital data between avionics components, such as sensors, flight computers, and control systems, to ensure coordinated and reliable operation.
-
C.
SAS protocol
SAS protocol is a serial communication protocol used primarily for connecting and transferring data between storage devices (like hard drives and SSDs) and host systems in enterprise environments.
-
D.
link-layer protocol
chosen
A link-layer protocol defines the rules and procedures for reliable data transfer, framing, addressing, and error handling between directly connected network devices on a physical medium.
-
E.
military bridge-layer system
A military bridge-layer system is an armored, mobile engineering vehicle designed to rapidly deploy and retrieve temporary bridges to enable troops and vehicles to cross obstacles in combat environments.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.