Triple
T21158917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Savers, Inc. |
E521383
|
entity |
| Predicate | hasProductFlavor |
P107732
|
FINISHED |
| Object | mint |
—
|
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: mint | Statement: [Life Savers, Inc., hasProductFlavor, mint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductFlavor Context triple: [Life Savers, Inc., hasProductFlavor, mint]
-
A.
hasFlavorType
chosen
Indicates that an entity possesses or is characterized by a particular type or category of flavor.
-
B.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasSecondaryFlavor
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
-
D.
isOfficialFlavorOf
Indicates that one item is formally recognized or designated as an official flavor associated with another entity (such as a brand, product line, or event).
-
E.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252e9ef481908f4904c535f3da8b |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.