Triple
T699995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media Mail |
E13976
|
entity |
| Predicate | extraServices |
P16033
|
FINISHED |
| Object | Signature Confirmation available |
—
|
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: Signature Confirmation available | Statement: [Media Mail, extraServices, Signature Confirmation available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extraServices Context triple: [Media Mail, extraServices, Signature Confirmation available]
-
A.
offeredService
chosen
Indicates that one entity has provided or made available a service to another entity.
-
B.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
C.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
D.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
E.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.