Triple
T12697351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosso Piceno |
E303369
|
entity |
| Predicate | aromaFlavorProfile |
P16142
|
FINISHED |
| Object | fruity |
—
|
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: fruity | Statement: [Rosso Piceno, aromaFlavorProfile, fruity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aromaFlavorProfile Context triple: [Rosso Piceno, aromaFlavorProfile, fruity]
-
A.
primaryAroma
Indicates the main or most dominant scent associated with an entity, distinguishing it from secondary or background aromas.
-
B.
wineCharacteristic
chosen
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
C.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
D.
coffeeFlavorNotes
Indicates the characteristic taste and aroma qualities associated with a particular coffee, such as specific flavor notes perceived when it is consumed.
-
E.
olfactoryFamily
Indicates a relationship where one entity belongs to, or is categorized within, a particular olfactory family or scent classification defined by the other 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.