Triple
T18254815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wish |
E437195
|
entity |
| Predicate | shippingModel |
P16612
|
FINISHED |
| Object | cross-border 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: cross-border shipping | Statement: [Wish, shippingModel, cross-border shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shippingModel Context triple: [Wish, shippingModel, cross-border shipping]
-
A.
shippingLine
Indicates a relationship where an entity is associated with, or transported via, a particular shipping line or carrier service.
-
B.
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).
-
C.
shippingAccess
Indicates that one entity has the ability or permission to ship items to or on behalf of another entity.
-
D.
shippingFunction
chosen
Indicates the method or process by which goods are transported or delivered from a sender to a recipient.
-
E.
ownedShippingLine
Indicates that one entity possessed legal ownership or controlling interest in a particular shipping line.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd84b3a481908bbc1a5e5034d397 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.