Triple
T3451152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic Privacy Browser |
E72795
|
entity |
| Predicate | dataCollectionPolicy |
P10529
|
FINISHED |
| Object | no search or browsing history stored on servers |
—
|
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: no search or browsing history stored on servers | Statement: [Epic Privacy Browser, dataCollectionPolicy, no search or browsing history stored on servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionPolicy Context triple: [Epic Privacy Browser, dataCollectionPolicy, no search or browsing history stored on servers]
-
A.
dataPolicy
chosen
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
B.
collectionPolicy
Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
-
C.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
D.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
E.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7465248190947f9096e230e1c4 |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.