Triple
T25521347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-38E |
E639658
|
entity |
| Predicate | specifiesAlgorithm |
P54503
|
FINISHED |
| Object | XTS-AES |
—
|
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: XTS-AES | Statement: [NIST SP 800-38E, specifiesAlgorithm, XTS-AES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesAlgorithm Context triple: [NIST SP 800-38E, specifiesAlgorithm, XTS-AES]
-
A.
associatedWithAlgorithm
Indicates that one entity has a connection or linkage to a specific algorithm, such as using, implementing, or being defined in terms of that algorithm.
-
B.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
C.
specifiesMethod
Indicates that one entity defines or designates the particular method or procedure by which another entity operates or is carried out.
-
D.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
E.
hasAlgorithmName
chosen
Indicates that an entity is associated with or identified by a specific algorithm name.
- F. None of above.
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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f836387c8190813f5c202ff47a8c |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3 p.m.