Triple
T32498158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Hash Standard |
E830581
|
entity |
| Predicate | firstVersionNumber |
—
|
GENERATED |
| Object | FIPS 180 |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVersionNumber Context triple: [Secure Hash Standard, firstVersionNumber, FIPS 180]
-
A.
firstReleaseVersion
chosen
Indicates the specific version identifier associated with the initial public release of something.
-
B.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
C.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
-
D.
firstDeveloperRelease
Indicates the date or version when a developer-focused or pre-release version of a product was first made available.
-
E.
firstMajorVersionBy
Indicates that one entity is the earliest or initial major version created or released by another entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.