Triple
T3837993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Express |
E91181
|
entity |
| Predicate | supportsDeclaredValueCoverage |
P42076
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UPS Worldwide Express, supportsDeclaredValueCoverage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeclaredValueCoverage Context triple: [UPS Worldwide Express, supportsDeclaredValueCoverage, yes]
-
A.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
B.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
C.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
-
D.
providesCoverage
chosen
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
E.
declaredOverBy
Indicates that one entity is formally announced, proclaimed, or made known through the authority or action 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb9d11f081909fc51e84657ec7f1 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.