Triple
T577327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health Connect |
E13783
|
entity |
| Predicate | privacyProperty |
P15698
|
FINISHED |
| Object | user can revoke app access at any time |
—
|
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: user can revoke app access at any time | Statement: [Health Connect, privacyProperty, user can revoke app access at any time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privacyProperty Context triple: [Health Connect, privacyProperty, user can revoke app access at any time]
-
A.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
B.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
-
C.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
publicOrPrivate
Indicates whether something is designated as publicly accessible or restricted to private use or access.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.