Triple

T8782126
Position Surface form Disambiguated ID Type / Status
Subject DNS over DTLS E208754 entity
Predicate isLessDeployedThan P85347 FINISHED
Object DNS over HTTPS 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: DNS over HTTPS | Statement: [DNS over DTLS, isLessDeployedThan, DNS over HTTPS]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLessDeployedThan
Context triple: [DNS over DTLS, isLessDeployedThan, DNS over HTTPS]
  • A. isDeployedFrom
    Indicates that one entity originates, is launched, or put into operation from another specified source or location.
  • B. hasDeployment
    Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
  • C. deployedTo
    Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
  • D. canBeDeployedUnder
    Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
  • E. deployedFor
    Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
  • F. None of above. chosen

Provenance (4 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_69ca835fbee88190bf625939bac48d7f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f7155b081908891e84b704f0ebf completed March 31, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69cc5c1aff3881908be6a9cbc9f50461 completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cfddef48190aee764ee7b25bae9 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:42 p.m.