Triple
T33057425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICKEY 2.0 |
E845878
|
entity |
| Predicate | initializationPhase |
P84870
|
FINISHED |
| Object | key and IV loading followed by mixing |
—
|
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: key and IV loading followed by mixing | Statement: [MICKEY 2.0, initializationPhase, key and IV loading followed by mixing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initializationPhase Context triple: [MICKEY 2.0, initializationPhase, key and IV loading followed by mixing]
-
A.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
-
B.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
C.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
D.
acquisitionPhase
Indicates the stage or phase within an overall acquisition process in which the related entities are currently involved.
-
E.
protocolPhase
chosen
Indicates the specific stage or step within a defined protocol or procedural sequence that an action, process, or entity is associated with.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:25 a.m.