Triple
T13965406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST Cybersecurity Framework |
E335908
|
entity |
| Predicate | version1.1ReleaseYear |
P111974
|
FINISHED |
| Object | 2018 |
—
|
LITERAL 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: 2018 | Statement: [NIST Cybersecurity Framework, version1.1ReleaseYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: version1.1ReleaseYear Context triple: [NIST Cybersecurity Framework, version1.1ReleaseYear, 2018]
-
A.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
B.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
C.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
D.
bestKnownVersionReleaseYear
Indicates the calendar year in which the most widely recognized or prominent version of something was released.
-
E.
ARVersionAnnouncementYear
Indicates the year in which a specific version of an augmented reality (AR) product or system was officially announced.
- F. None of above. chosen
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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7e24f08190ba939a8044860033 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.