Triple
T16702662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firefox Relay |
E405889
|
entity |
| Predicate | dataProcessed |
P96786
|
FINISHED |
| Object | incoming emails to aliases |
—
|
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: incoming emails to aliases | Statement: [Firefox Relay, dataProcessed, incoming emails to aliases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProcessed Context triple: [Firefox Relay, dataProcessed, incoming emails to aliases]
-
A.
dataProcessingStyle
Indicates the manner, method, or approach by which data is processed or handled in a given context.
-
B.
data
chosen
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
C.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
D.
dataProcessingInequality
Indicates that processing data through a (possibly noisy) transformation cannot increase the information one variable has about another, so the mutual information between them can only stay the same or decrease.
-
E.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38333a6908190a17d2dee2ca622d6 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.