Triple
T17524273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvia officinalis |
E426754
|
entity |
| Predicate | aromaSource |
P95361
|
FINISHED |
| Object | essential oils |
—
|
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: essential oils | Statement: [Salvia officinalis, aromaSource, essential oils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aromaSource Context triple: [Salvia officinalis, aromaSource, essential oils]
-
A.
agingAromaDevelopment
Indicates the process by which an aroma changes and develops over time as something ages.
-
B.
aromaticOilsPresent
chosen
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
C.
primaryAroma
Indicates the main or most dominant scent associated with an entity, distinguishing it from secondary or background aromas.
-
D.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d4db60819096a03dbc4254850f |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.