Triple

T1711737
Position Surface form Disambiguated ID Type / Status
Subject TLS 1.2 Finished message E37197 entity
Predicate verify_dataLength P28891 FINISHED
Object 12 bytes for non-export cipher suites 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: 12 bytes for non-export cipher suites | Statement: [TLS 1.2 Finished message, verify_dataLength, 12 bytes for non-export cipher suites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: verify_dataLength
Context triple: [TLS 1.2 Finished message, verify_dataLength, 12 bytes for non-export cipher suites]
  • A. hasFieldLength chosen
    Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
  • B. properLengthMeasuredIn
    Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
  • C. supportsTagLength
    Indicates that an entity is capable of handling or enforcing a specified tag length.
  • D. supportsKeyLength
    Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
  • E. isFeatureLength
    Indicates that something (typically a film or video) has a duration long enough to be considered a full-length, standard feature.
  • 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.