Triple

T306742
Position Surface form Disambiguated ID Type / Status
Subject HTTP/2 E6319 entity
Predicate canBeUsedOver P10654 FINISHED
Object TLS E1268 NE FINISHED

How this triple was built (3 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 | Statement: [HTTP/2, canBeUsedOver, TLS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS
Context triple: [HTTP/2, canBeUsedOver, TLS]
  • A. TLS chosen
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • B. SSL
    SSL (Secure Sockets Layer) is a cryptographic protocol designed to provide secure, encrypted communication over a computer network, commonly used to protect data transmitted between clients and servers.
  • C. HTTPS
    HTTPS is the secure version of the HTTP protocol that encrypts data exchanged between a client and server to protect confidentiality and integrity on the web.
  • D. TLS 1.1
    TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
  • E. TLS 1.0
    TLS 1.0 is an early version of the Transport Layer Security protocol used to secure communications over computer networks, now largely deprecated in favor of more secure later versions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeUsedOver
Context triple: [HTTP/2, canBeUsedOver, TLS]
  • A. canUse
    Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
  • B. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
  • C. eligibleUses
    Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
  • D. canAlsoBe
    Indicates that something has an additional possible state, role, or classification beyond its primary one.
  • E. usedOn
    Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
  • F. None of above. chosen

Provenance (5 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_69a2e79230508190b912ecb555aae17e completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea313be88190b4441f3ea41a99e2 completed Feb. 28, 2026, 1:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3c8b480388190b5f7f9e11479de91 completed March 1, 2026, 5:03 a.m.
PD Predicate disambiguation batch_69a2e93db11881909b07ba5e76d91feb completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea07e3bc8190bae593b3264de211 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:06 p.m.