Triple
T19794893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettle Brand Sea Salt & Vinegar potato chips |
E475514
|
entity |
| Predicate | cutStyle |
P75445
|
FINISHED |
| Object | thick-cut |
—
|
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: thick-cut | Statement: [Kettle Brand Sea Salt & Vinegar potato chips, cutStyle, thick-cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutStyle Context triple: [Kettle Brand Sea Salt & Vinegar potato chips, cutStyle, thick-cut]
-
A.
cuttingStyle
chosen
Indicates the manner or technique in which something is cut or shaped.
-
B.
cutFormat
Indicates that one entity trims or shapes another entity into a specified format or pattern.
-
C.
cutRule
Indicates that one entity applies or enforces a rule that removes, prunes, or eliminates certain elements or possibilities from consideration.
-
D.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
E.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c659088190928fa4c9264135d3 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.