Triple
T33057138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-128 |
E845872
|
entity |
| Predicate | statusIn eSTREAM |
P175758
|
FINISHED |
| Object | recommended algorithm |
—
|
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: recommended algorithm | Statement: [HC-128, statusIn eSTREAM, recommended algorithm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusIn eSTREAM Context triple: [HC-128, statusIn eSTREAM, recommended algorithm]
-
A.
categoryIn eSTREAM
chosen
Indicates that something belongs to or is classified within the eSTREAM category.
-
B.
cryptanalysisStatus
Indicates the current state or outcome of efforts to analyze or break a cryptographic system or cipher.
-
C.
AESFinalistCount
Indicates the number of entities that have reached the final stage in an AES-related competition or evaluation.
-
D.
AESWinner
Indicates that an entity has won an AES (Association for Education in Journalism and Mass Communication) award or competition.
-
E.
wasAESFinalist
Indicates that an entity was selected as a finalist in the Advanced Encryption Standard (AES) competition.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:25 a.m.