Triple
T17675381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action Mailer |
E440630
|
entity |
| Predicate | supportsDeliveryMethod |
P15886
|
FINISHED |
| Object | smtp |
—
|
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: smtp | Statement: [Action Mailer, supportsDeliveryMethod, smtp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeliveryMethod Context triple: [Action Mailer, supportsDeliveryMethod, smtp]
-
A.
supportsSmartDelivery
Indicates that an entity provides or is compatible with a smart delivery mechanism that optimizes how content or items are delivered to recipients.
-
B.
supportsShippingMethods
Indicates that one entity enables or is compatible with the use of specific shipping methods for another entity.
-
C.
offersDelivery
Indicates that a provider makes goods or services available to be transported and delivered to a recipient’s specified location.
-
D.
ballDeliveryMethod
Indicates the manner or technique by which a ball is delivered, passed, or thrown from one entity to another.
-
E.
deliveryType
chosen
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.