Triple
T30895896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS express mail |
E787020
|
entity |
| Predicate | deliverySpeedComparedTo |
P170278
|
FINISHED |
| Object | faster than standard mail |
—
|
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: faster than standard mail | Statement: [EMS express mail, deliverySpeedComparedTo, faster than standard mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliverySpeedComparedTo Context triple: [EMS express mail, deliverySpeedComparedTo, faster than standard mail]
-
A.
deliverySpeed
Indicates the rate or promptness with which an item, service, or information is delivered from a source to a recipient.
-
B.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
C.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
D.
deliveryDays
Indicates the number of days required for an item or service to be delivered from the sender to the recipient.
-
E.
typicalDelivery
Indicates the usual or standard way in which something is delivered, reflecting the most common delivery method or pattern in that context.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923baa1081909407a75d6c22a34f |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.