Triple
T3521285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenmore |
E74426
|
entity |
| Predicate | typicalSalesChannel |
P35642
|
FINISHED |
| Object | brick-and-mortar retail |
—
|
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: brick-and-mortar retail | Statement: [Kenmore, typicalSalesChannel, brick-and-mortar retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSalesChannel Context triple: [Kenmore, typicalSalesChannel, brick-and-mortar retail]
-
A.
salesChannels
chosen
Indicates the channels or methods through which a product or service is marketed, sold, or distributed to customers.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
tradeMedium
Indicates that one entity serves as the medium or instrument through which another entity conducts trade or exchange transactions.
-
D.
saleType
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
E.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4c6ac8819096e9c773f3cccbfb |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.