Triple
T5016697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hide My Email |
E112754
|
entity |
| Predicate | emailDomainType |
P52128
|
FINISHED |
| Object | Apple-controlled relay domains |
—
|
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: Apple-controlled relay domains | Statement: [Hide My Email, emailDomainType, Apple-controlled relay domains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emailDomainType Context triple: [Hide My Email, emailDomainType, Apple-controlled relay domains]
-
A.
emailAddressDomain
Indicates that one entity is the domain portion (e.g., "example.com") of another entity’s email address.
-
B.
typicalDomain
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
C.
internetDomainTypeManaged
chosen
Indicates that the internet domain is administered or controlled by a managing authority or organization.
-
D.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
E.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.