Triple
T720755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priority Mail |
E14610
|
entity |
| Predicate | deliveryDays |
P18531
|
FINISHED |
| Object | Monday through Saturday |
—
|
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: Monday through Saturday | Statement: [Priority Mail, deliveryDays, Monday through Saturday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliveryDays Context triple: [Priority Mail, deliveryDays, Monday through Saturday]
-
A.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
B.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
C.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
ultimateFulfillmentAt
Indicates that something reaches its highest or final state of completion, satisfaction, or realization at a specified point, place, or condition.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58fa41c819082de2cc4e0cb2943 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.