Triple
T32971229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Creamery |
E843522
|
entity |
| Predicate | hasQualityClaim |
P78374
|
FINISHED |
| Object | award-winning cheddar |
—
|
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: award-winning cheddar | Statement: [Cabot Creamery, hasQualityClaim, award-winning cheddar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualityClaim Context triple: [Cabot Creamery, hasQualityClaim, award-winning cheddar]
-
A.
hasQualityModel
Indicates that an entity is associated with or characterized by a specific quality model.
-
B.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
C.
hasMarketingClaim
chosen
Indicates that an entity asserts or is associated with a specific marketing claim about a product, service, or brand.
-
D.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
E.
hasQualityControl
Indicates that an entity is subject to processes or measures designed to monitor, verify, and maintain the quality of its outputs or operations.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1aa6c6481909e8e2968d4f3029d |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.