Triple
T26408555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | AESDesignBasis |
P160521
|
FINISHED |
| Object | subset of Rijndael with 128-bit block size |
—
|
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: subset of Rijndael with 128-bit block size | Statement: [NIST, AESDesignBasis, subset of Rijndael with 128-bit block size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESDesignBasis Context triple: [NIST, AESDesignBasis, subset of Rijndael with 128-bit block size]
-
A.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
B.
basedOnDesignBy
Indicates that something is created, developed, or structured according to the design conceived or produced by a specified entity.
-
C.
designStandardizedIn
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
-
D.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
E.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:36 p.m.