Triple
T3837979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Express |
E91181
|
entity |
| Predicate | deliveryScope |
P52300
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [UPS Worldwide Express, deliveryScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryScope Context triple: [UPS Worldwide Express, deliveryScope, international]
-
A.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
B.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
C.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
D.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
-
E.
deliveryMode
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:18 p.m.