Triple
T30895899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS express mail |
E787020
|
entity |
| Predicate | hasServiceLevelOption |
P59249
|
FINISHED |
| Object | next-day delivery in some domestic markets |
—
|
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: next-day delivery in some domestic markets | Statement: [EMS express mail, hasServiceLevelOption, next-day delivery in some domestic markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceLevelOption Context triple: [EMS express mail, hasServiceLevelOption, next-day delivery in some domestic markets]
-
A.
hasServiceStandard
Indicates that an entity is associated with, or governed by, a defined service standard specifying expected service levels or quality.
-
B.
hasLimitedServiceType
Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
-
C.
hasPassengerServiceLevel
Indicates the level or quality of passenger service provided in a given transportation context.
-
D.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
E.
hasServiceVariations
chosen
Indicates that a service is offered in multiple distinct versions, options, or configurations that differ in some defined characteristics.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 29, 2026, 8:49 p.m.