Triple
T32136215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RedPepperFlakes |
E820769
|
entity |
| Predicate | hasSecondaryTaste |
P104049
|
FINISHED |
| Object | slightly smoky |
—
|
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: slightly smoky | Statement: [RedPepperFlakes, hasSecondaryTaste, slightly smoky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryTaste Context triple: [RedPepperFlakes, hasSecondaryTaste, slightly smoky]
-
A.
hasSecondaryFlavor
chosen
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
-
B.
hasTasteIntensity
Indicates the degree or strength of taste associated with something.
-
C.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
D.
notableFlavorNotes
Indicates that something is characterized by specific, distinguishable flavor notes that are especially prominent or noteworthy.
-
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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 12:30 a.m.