Triple
T3874944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Worldwide Saver |
E92477
|
entity |
| Predicate | serviceUseCase |
P52084
|
FINISHED |
| Object | urgent international documents |
—
|
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: urgent international documents | Statement: [UPS Worldwide Saver, serviceUseCase, urgent international documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceUseCase Context triple: [UPS Worldwide Saver, serviceUseCase, urgent international documents]
-
A.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
B.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
C.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
D.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
E.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.