Triple
T1711740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.2 Finished message |
E37197
|
entity |
| Predicate | PRFInput |
P19412
|
FINISHED |
| Object | master secret |
—
|
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: master secret | Statement: [TLS 1.2 Finished message, PRFInput, master secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PRFInput Context triple: [TLS 1.2 Finished message, PRFInput, master secret]
-
A.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
B.
input
chosen
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
C.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
D.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
E.
parameter
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.