Triple
T3419547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject |
E72083
|
entity | |
| Predicate | privacyModel |
P15689
|
FINISHED |
| Object | end-to-end encrypted personal messages |
—
|
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: end-to-end encrypted personal messages | Statement: [WhatsApp, privacyModel, end-to-end encrypted personal messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privacyModel Context triple: [WhatsApp, privacyModel, end-to-end encrypted personal messages]
-
A.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
B.
privacyCharacteristic
chosen
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
-
C.
privacyPolicyURL
Indicates the web address where the privacy policy governing data collection and use can be accessed.
-
D.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
E.
explainsPolicy
Indicates that one entity provides a clarification or detailed description of a policy to 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94d6808819080997df30119e71e |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.