Triple
T13175973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO tactical data links |
E313099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical data link standard |
C2464
|
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 standard Context triple: [NATO tactical data links, instanceOf, tactical data link standard]
-
A.
military standard
chosen
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
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.
implementation mechanism for ICAO Standards and Recommended Practices
A structured set of legal, administrative, and technical processes through which States adopt, adapt, and apply ICAO Standards and Recommended Practices within their national civil aviation systems.
-
D.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.