Triple
T36553601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH KEXINIT message |
E901637
|
entity |
| Predicate | cookiePurpose |
P79
|
FINISHED |
| Object | randomness to thwart certain attacks |
—
|
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: randomness to thwart certain attacks | Statement: [SSH KEXINIT message, cookiePurpose, randomness to thwart certain attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cookiePurpose Context triple: [SSH KEXINIT message, cookiePurpose, randomness to thwart certain attacks]
-
A.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
B.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
C.
secretPurpose
Indicates that an entity has an underlying goal, intention, or function that is deliberately concealed or not openly disclosed.
-
D.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
E.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.