Triple
T31498280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mail Privacy Protection |
E803606
|
entity |
| Predicate | impactOnSenders |
P58916
|
FINISHED |
| Object | reduces reliability of open tracking metrics |
—
|
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: reduces reliability of open tracking metrics | Statement: [Mail Privacy Protection, impactOnSenders, reduces reliability of open tracking metrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnSenders Context triple: [Mail Privacy Protection, impactOnSenders, reduces reliability of open tracking metrics]
-
A.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
B.
encodingImpact
Indicates how one encoding or encoding choice affects, modifies, or constrains another process, representation, or outcome.
-
C.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
D.
effectOnOthers
chosen
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
E.
impactOnPublisher
Indicates the effect or consequences that an action, event, or entity has on the publisher.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 30, 2026, 9:42 p.m.