Triple
T37625347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pikesville Rye |
E936191
|
entity |
| Predicate | notableAromaNotes |
P71396
|
FINISHED |
| Object | baking spices |
—
|
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: baking spices | Statement: [Pikesville Rye, notableAromaNotes, baking spices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAromaNotes Context triple: [Pikesville Rye, notableAromaNotes, baking spices]
-
A.
notableFlavorNotes
Indicates that something is characterized by specific, distinguishable flavor notes that are especially prominent or noteworthy.
-
B.
characteristicAroma
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
C.
primaryAroma
chosen
Indicates the main or most dominant scent associated with an entity, distinguishing it from secondary or background aromas.
-
D.
wineCharacteristic
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
E.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.