Triple

T10532259
Position Surface form Disambiguated ID Type / Status
Subject SHA-256 E248473 entity
Predicate definedInStandard P1371 FINISHED
Object FIPS 180-2 E869767 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: FIPS 180-2 | Statement: [SHA-256, definedInStandard, FIPS 180-2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FIPS 180-2
Context triple: [SHA-256, definedInStandard, FIPS 180-2]
  • A. FIPS 180-4 chosen
    FIPS 180-4 is a U.S. federal information processing standard that specifies the Secure Hash Standard (SHS), including widely used cryptographic hash functions such as SHA-256.
  • B. FIPS 198-1
    FIPS 198-1 is a U.S. federal information processing standard that specifies the security requirements and implementation details for the HMAC (Hash-based Message Authentication Code) algorithm.
  • C. FIPS 186-2
    FIPS 186-2 is a U.S. federal standard specifying approved digital signature algorithms, including updates and formal definitions for methods such as ECDSA used in government and security applications.
  • D. SHA-2
    SHA-2 is a family of cryptographic hash functions widely used for data integrity, digital signatures, and security protocols on the internet.
  • E. Secure Hash Standard
    The Secure Hash Standard is a U.S. federal standard that specifies secure hash algorithms (such as the SHA family) used for generating fixed-size cryptographic hashes to ensure data integrity and support digital signatures.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d381c5c7448190bec34bee7ec72bac completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d50a17f23081909f3372e160e21670 completed April 7, 2026, 1:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69d933fffc4c81908798094f72a06d18 completed April 10, 2026, 5:31 p.m.
Created at: April 6, 2026, 12:30 p.m.