Triple
T29439035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS over HTTPS |
E746659
|
entity |
| Predicate | encryptionProvidedBy |
P143142
|
FINISHED |
| Object | TLS |
—
|
NE NERFINISHED |
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: TLS | Statement: [DNS over HTTPS, encryptionProvidedBy, TLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionProvidedBy Context triple: [DNS over HTTPS, encryptionProvidedBy, TLS]
-
A.
encryptionIs
Indicates that one entity serves as the encryption method, state, or property applied to another entity.
-
B.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
C.
dataIsEncrypted
Indicates that the referenced data is stored or transmitted in an encrypted form rather than in plaintext.
-
D.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
-
E.
encryptionProtocol
chosen
Indicates that one entity uses, specifies, or is governed by a particular method or standard for encrypting data in its communications or storage.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1b4be08190b2ccb9612c9bcb4e |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:19 p.m.