Triple
T33076880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECRYPT II |
E846387
|
entity |
| Predicate | objectiveOfInitiative |
P64674
|
FINISHED |
| Object | evaluation of stream cipher proposals |
—
|
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: evaluation of stream cipher proposals | Statement: [ECRYPT II, objectiveOfInitiative, evaluation of stream cipher proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfInitiative Context triple: [ECRYPT II, objectiveOfInitiative, evaluation of stream cipher proposals]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
initiative
Indicates that an entity takes the first step or leads in starting an action, project, or process without external prompting.
-
C.
aimOfCampaign
Indicates that a campaign is directed toward achieving a particular goal or objective.
-
D.
USObjectives
Indicates that the relationship specifies the goals, aims, or strategic objectives pursued by the United States in a given context or situation.
-
E.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.