Triple
T6790476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varien Inc. |
E155917
|
entity |
| Predicate | mainProductCategory |
P64612
|
FINISHED |
| Object | shopping cart software |
—
|
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: shopping cart software | Statement: [Varien Inc., mainProductCategory, shopping cart software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProductCategory Context triple: [Varien Inc., mainProductCategory, shopping cart software]
-
A.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
B.
coreCategory
chosen
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
offersProductCategory
Indicates that a provider or seller makes products belonging to a specific product category available.
-
E.
categoryIUsedFor
Indicates that one entity is used as a category or classification label for another entity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2acbfc0819081f2d6cebfb91765 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.