Triple
T3874940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Saver |
E92477
|
entity |
| Predicate | pickupOptions |
P18532
|
FINISHED |
| Object | scheduled pickup |
—
|
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: scheduled pickup | Statement: [UPS Worldwide Saver, pickupOptions, scheduled pickup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pickupOptions Context triple: [UPS Worldwide Saver, pickupOptions, scheduled pickup]
-
A.
pickupOption
chosen
Indicates that one entity offers or selects a method or arrangement for collecting or retrieving another entity (such as goods, items, or services).
-
B.
pickupConfiguration
Indicates the specific arrangement or setup in which one entity is collected, retrieved, or picked up by another.
-
C.
dropOffOptions
Indicates the available ways, locations, or conditions under which something can be dropped off or delivered.
-
D.
dropOffOption
Indicates an available method or arrangement by which something can be left or delivered at a specified location.
-
E.
takesAway
Indicates that one entity removes, deprives, or causes another entity to lose something it previously had.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.