Triple

T1096785
Position Surface form Disambiguated ID Type / Status
Subject Secure Real-time Transport Protocol E24287 entity
Predicate keyManagement P5660 FINISHED
Object out-of-band key management required 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: out-of-band key management required | Statement: [Secure Real-time Transport Protocol, keyManagement, out-of-band key management required]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: keyManagement
Context triple: [Secure Real-time Transport Protocol, keyManagement, out-of-band key management required]
  • A. keyManagementType chosen
    Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
  • B. keyProvision
    Indicates that one entity serves as a primary or essential provision, resource, or supply for another entity.
  • C. keyAgreement
    Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
  • D. keyComponent
    Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
  • E. key
    Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b99ffb3481908cd168b6c58e1c6d completed March 1, 2026, 10:11 p.m.
PD Predicate disambiguation batch_69a4b7448c148190a3c9a4158ebd05b4 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.