Triple
T26408574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | AESFinalists |
P105392
|
FINISHED |
| Object | Serpent |
—
|
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: Serpent | Statement: [NIST, AESFinalists, Serpent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESFinalists Context triple: [NIST, AESFinalists, Serpent]
-
A.
wasAESFinalist
chosen
Indicates that an entity was selected as a finalist in the Advanced Encryption Standard (AES) competition.
-
B.
AESWinner
Indicates that an entity has won an AES (Association for Education in Journalism and Mass Communication) award or competition.
-
C.
AESFinalistCount
Indicates the number of entities that have reached the final stage in an AES-related competition or evaluation.
-
D.
cryptDesigner
Indicates that an entity is the designer or creator responsible for planning or conceiving a particular crypt.
-
E.
Merkle–Damgård strengthening
Indicates that a hash function construction applies Merkle–Damgård strengthening, meaning the message is padded with its length (and possibly other structured padding) before processing to help ensure collision resistance and proper security properties.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:36 p.m.