Triple

T29503786
Position Surface form Disambiguated ID Type / Status
Subject Basic E748454 entity
Predicate transmissionSecurityProperty P135211 FINISHED
Object credentials are not encrypted by the scheme itself 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: credentials are not encrypted by the scheme itself | Statement: [Basic, transmissionSecurityProperty, credentials are not encrypted by the scheme itself]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transmissionSecurityProperty
Context triple: [Basic, transmissionSecurityProperty, credentials are not encrypted by the scheme itself]
  • A. securesProtocol
    Indicates that one entity protects, safeguards, or enforces the security of a communication or operational protocol for another entity.
  • B. encryptionProtocol
    Indicates that one entity uses, specifies, or is governed by a particular method or standard for encrypting data in its communications or storage.
  • C. protocolProperty chosen
    Indicates that a specific property or characteristic is defined or governed by a particular protocol.
  • D. supportsEncryptionInTransit
    Indicates that one entity provides or enables protection of data while it is being transmitted between entities.
  • E. hasSecureCommunications
    Indicates that one entity maintains protected, confidential, and tamper-resistant channels for exchanging information with 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_69f0bd455a9c8190b40a3e8ea38cf61f completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fd67191cf88190b53ecbf5be3564e9 completed May 8, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69fd654fdaac81908e67e75194710f06 completed May 8, 2026, 4:23 a.m.
Created at: April 28, 2026, 4:26 p.m.