Triple
T35490313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Variable Message Format |
E1025714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical data link message 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 message standard Context triple: [Variable Message Format, instanceOf, tactical data link message 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.
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.
-
C.
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.
-
D.
military signal
A military signal is a transmitted message, visual cue, or coded communication used by armed forces to convey orders, information, or intentions in a coordinated and secure manner.
-
E.
meteorological data communication network
A meteorological data communication network is a system of interconnected sensors, transmission links, and processing nodes that collect, transmit, and distribute weather and atmospheric data in real time.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.