Triple
T29439038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS over HTTPS |
E746659
|
entity |
| Predicate | doesNotHide |
P167969
|
FINISHED |
| Object | destination IP addresses |
—
|
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: destination IP addresses | Statement: [DNS over HTTPS, doesNotHide, destination IP addresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotHide Context triple: [DNS over HTTPS, doesNotHide, destination IP addresses]
-
A.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
B.
doesNotProtect
Indicates that an entity fails to provide protection or safeguarding to another entity or object.
-
C.
notTypicallyShownTo
Indicates that one entity is generally not displayed or presented to another entity under normal circumstances.
-
D.
doesNotCover
Indicates that one entity fails to include, protect, or extend over another entity or area.
-
E.
notVisibleWhen
Indicates that one entity is not visible whenever a specified condition, state, or context involving another entity holds.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 3:19 p.m.