Triple
T13894842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RocketMail |
E334060
|
entity |
| Predicate | emailProtocolSupport |
P35980
|
FINISHED |
| Object | webmail |
—
|
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: webmail | Statement: [RocketMail, emailProtocolSupport, webmail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emailProtocolSupport Context triple: [RocketMail, emailProtocolSupport, webmail]
-
A.
supportsPushEmail
Indicates that one entity provides or enables automatic, real-time delivery of email (push email) to another entity.
-
B.
emailSupport
Indicates that one entity provides assistance or help to another via email communication.
-
C.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.