Triple
T33057161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-128 |
E845872
|
entity |
| Predicate | keySetup |
P175759
|
FINISHED |
| Object | initializes internal state from key and IV |
—
|
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: initializes internal state from key and IV | Statement: [HC-128, keySetup, initializes internal state from key and IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySetup Context triple: [HC-128, keySetup, initializes internal state from key and IV]
-
A.
keyOutput
Indicates that an entity functions as a primary or essential result, product, or outcome produced by another entity or process.
-
B.
keyProvision
Indicates that one entity serves as a primary or essential provision, resource, or supply for another entity.
-
C.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
-
D.
keyPlan
Indicates that an entity serves as or contains the primary plan, blueprint, or guiding scheme for another entity or process.
-
E.
keySupplication
Indicates a relationship where one entity earnestly petitions or implores another for something considered crucial or decisive.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.