Triple
T18276342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-1 |
E437745
|
entity |
| Predicate | partOfStandard |
P35
|
FINISHED |
| Object | FIPS 180-1 |
—
|
NE NERFINISHED |
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-1 | Statement: [SHA-1, partOfStandard, FIPS 180-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FIPS 180-1 Context triple: [SHA-1, partOfStandard, FIPS 180-1]
-
A.
FIPS 180-1
chosen
FIPS 180-1 is a U.S. federal information processing standard that specifies the Secure Hash Algorithm (SHA-1) for use in cryptographic applications.
-
B.
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.
-
C.
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.
-
D.
FIPS 186-3
FIPS 186-3 is a U.S. federal standard that specifies approved digital signature algorithms and requirements for secure digital signatures.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500528bb88190a9f9ba6428cc2076 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 10:34 a.m.