Triple
T3837996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Express |
E91181
|
entity |
| Predicate | bookingChannels |
P31089
|
FINISHED |
| Object | UPS website |
—
|
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: UPS website | Statement: [UPS Worldwide Express, bookingChannels, UPS website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingChannels Context triple: [UPS Worldwide Express, bookingChannels, UPS website]
-
A.
airlineBookingChannel
Indicates the method or platform through which an airline reservation is made or managed between a customer and the airline.
-
B.
hasBookingChannel
chosen
Indicates that an entity is associated with or obtained through a particular method or platform used to make a booking.
-
C.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
D.
hotelConnection
Indicates a relationship where one entity is linked or associated with a hotel, such as being located in, connected to, or serviced by that hotel.
-
E.
hotelOperator
Indicates that an entity operates, manages, or runs a hotel as its responsible service provider or business owner.
- 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.