Triple
T31176313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiano di Avellino wine |
E794758
|
entity |
| Predicate | aromaDevelopmentWithAge |
P104592
|
FINISHED |
| Object | honeyed notes |
—
|
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: honeyed notes | Statement: [Fiano di Avellino wine, aromaDevelopmentWithAge, honeyed notes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aromaDevelopmentWithAge Context triple: [Fiano di Avellino wine, aromaDevelopmentWithAge, honeyed notes]
-
A.
agingAromaDevelopment
chosen
Indicates the process by which an aroma changes and develops over time as something ages.
-
B.
characteristicAroma
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
C.
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.
-
D.
senseOfSmell
Indicates that one entity has the ability to detect or perceive odors or scents through the sense of smell.
-
E.
flavorProfileChangeWithAge
Indicates how the flavor characteristics of something evolve or change as it ages.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.