Triple
T27614283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIPS 140 |
E700397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government standard |
C22172
|
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: U.S. government standard Context triple: [FIPS 140, instanceOf, U.S. government standard]
-
A.
United States agricultural standard
A United States agricultural standard is an officially established set of criteria and specifications that define the quality, grade, and handling requirements for agricultural products within the U.S. regulatory framework.
-
B.
official standard
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
-
C.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
D.
military standard
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.
-
E.
U.S. government encryption standard
chosen
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:12 p.m.