Triple
T4554364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WooCommerce |
E120445
|
entity |
| Predicate | supportsShippingMethods |
P57983
|
FINISHED |
| Object | flat rate 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: flat rate shipping | Statement: [WooCommerce, supportsShippingMethods, flat rate shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsShippingMethods Context triple: [WooCommerce, supportsShippingMethods, flat rate shipping]
-
A.
supportsPackageShipments
Indicates that one entity provides the capability or service needed to handle and transport package shipments for another entity.
-
B.
supportsNonDocumentShipments
Indicates that the carrier or service is able to handle and transport shipments that consist of non-document items (e.g., goods, merchandise, or parcels).
-
C.
supportsDocumentShipments
Indicates that an entity is capable of handling or enabling the shipment of documents.
-
D.
containsShippingRoute
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
E.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58127ed08190a04962a43afb888b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:09 p.m.