Triple
T38373114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypted Client Hello |
E893544
|
entity |
| Predicate | usesProtocolVersion |
P176735
|
FINISHED |
| Object | TLS 1.3 |
—
|
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: TLS 1.3 | Statement: [Encrypted Client Hello, usesProtocolVersion, TLS 1.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProtocolVersion Context triple: [Encrypted Client Hello, usesProtocolVersion, TLS 1.3]
-
A.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
B.
usesProtocolValue
chosen
Indicates that one entity operates according to, or communicates using, a specified protocol value.
-
C.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
D.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
E.
relatedToProtocolVersion
Indicates a relationship where something is associated with, governed by, or dependent on a specific protocol version.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:31 p.m.