Triple
T752938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priority Mail Express |
E15488
|
entity |
| Predicate | optionalService |
P9404
|
FINISHED |
| Object | additional insurance |
—
|
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: additional insurance | Statement: [Priority Mail Express, optionalService, additional insurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalService Context triple: [Priority Mail Express, optionalService, additional insurance]
-
A.
offeredService
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.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
D.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64d7d2c8190a6059adcb8fbd34f |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.