Triple
T4147493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPS Ground |
E89819
|
entity |
| Predicate | returnServiceType |
P18393
|
FINISHED |
| Object | UPS Returns via ground |
—
|
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 Returns via ground | Statement: [UPS Ground, returnServiceType, UPS Returns via ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnServiceType Context triple: [UPS Ground, returnServiceType, UPS Returns via ground]
-
A.
returnService
chosen
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
B.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
C.
returnBasis
Indicates the basis, method, or terms under which something is returned (e.g., goods, funds, or data) from one party or context to another.
-
D.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
E.
resultType
Indicates the type or category of outcome that is produced by a given process, action, or operation.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.