Triple
T13242074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reddaway |
E315303
|
entity |
| Predicate | shippingOption |
P16612
|
FINISHED |
| Object | next-day shipping |
—
|
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 shipping | Statement: [Reddaway, shippingOption, next-day shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingOption Context triple: [Reddaway, shippingOption, next-day shipping]
-
A.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
B.
shippingFunction
chosen
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
C.
shippingLaneFor
Indicates that one entity serves as a designated shipping lane or route used for the transportation or navigation of another entity (such as ships or cargo).
-
D.
supportsShippingMethods
Indicates that one entity enables or is compatible with the use of specific shipping methods for another entity.
-
E.
dropOffOption
Indicates an available method or arrangement by which something can be left or delivered at a specified location.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.