Triple
T22028248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla Enhanced Tracking Protection |
E544019
|
entity |
| Predicate | usesListFrom |
P144350
|
FINISHED |
| Object | Disconnect tracking protection lists |
—
|
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: Disconnect tracking protection lists | Statement: [Mozilla Enhanced Tracking Protection, usesListFrom, Disconnect tracking protection lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesListFrom Context triple: [Mozilla Enhanced Tracking Protection, usesListFrom, Disconnect tracking protection lists]
-
A.
usesList
chosen
Indicates that one entity employs or relies on another entity in the form of a list or ordered collection.
-
B.
listsAmong
Indicates that one entity includes or enumerates another entity as part of a list or collection.
-
C.
canList
Indicates that an entity has the ability or permission to enumerate or display a collection of items.
-
D.
listAPurpose
Indicates that an entity enumerates or specifies the purposes, goals, or intended uses associated with another entity.
-
E.
listsExample
Indicates that one entity provides or enumerates another entity as an example within a list.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.