Triple

T12515597
Position Surface form Disambiguated ID Type / Status
Subject DSA E299183 entity
Predicate standardRevision P84003 FINISHED
Object FIPS 186-2 E831962 NE FINISHED

How this triple was built (3 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 186-2 | Statement: [DSA, standardRevision, FIPS 186-2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FIPS 186-2
Context triple: [DSA, standardRevision, FIPS 186-2]
  • A. FIPS 186-2 chosen
    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.
  • 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 140
    FIPS 140 is a U.S. government standard that specifies security requirements for cryptographic modules used to protect sensitive information in computer and telecommunications systems.
  • D. FIPS 201
    FIPS 201 is a U.S. federal standard that defines the requirements and architecture for secure, interoperable personal identity verification (PIV) credentials for federal employees and contractors.
  • E. FIPS 180-4
    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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardRevision
Context triple: [DSA, standardRevision, FIPS 186-2]
  • A. standardReference
    Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
  • B. revisedByStandard chosen
    Indicates that something has been updated or modified in accordance with a specified standard or set of standards.
  • C. standardCreated
    Indicates that an entity is responsible for the creation or establishment of a particular standard.
  • D. standardMaintained
    Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
  • E. standardNumber
    Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
  • F. None of above.

Provenance (4 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d954b867dc8190af8a70f797e4d133 completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f655745cec8190b5582eb4a339d501 completed May 2, 2026, 7:50 p.m.
PD Predicate disambiguation batch_69d954096af88190b6be81b008c82139 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 9:57 p.m.