Triple
T16222174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS international services |
E393754
|
entity |
| Predicate | supportsShipmentMode |
P57983
|
FINISHED |
| Object | air freight |
—
|
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: air freight | Statement: [UPS international services, supportsShipmentMode, air freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsShipmentMode Context triple: [UPS international services, supportsShipmentMode, air freight]
-
A.
supportsPackageShipments
Indicates that one entity provides the capability or service needed to handle and transport package shipments for another entity.
-
B.
supportsShippingMethods
chosen
Indicates that one entity enables or is compatible with the use of specific shipping methods for another entity.
-
C.
supportsNonDocumentShipments
Indicates that the carrier or service is able to handle and transport shipments that consist of non-document items (e.g., goods, merchandise, or parcels).
-
D.
supportsDocumentShipments
Indicates that an entity is capable of handling or enabling the shipment of documents.
-
E.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227fcf058819099d5ff965cc2c267 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.