Triple
T699942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USPS Retail Ground |
E13975
|
entity |
| Predicate | returnService |
P18393
|
FINISHED |
| Object | supports returns |
—
|
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: supports returns | Statement: [USPS Retail Ground, returnService, supports returns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnService Context triple: [USPS Retail Ground, returnService, supports returns]
-
A.
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.
-
B.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
C.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
D.
publicServiceRemit
Indicates that an entity has an official obligation or mandate to provide services in the public interest, typically under a defined public-service framework or regulation.
-
E.
refundPolicy
Indicates the terms and conditions under which payments are returned or compensated after a purchase or transaction.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a54235548190b46218ea18f77341 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:36 p.m.