Triple
T17987692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coriandrum sativum |
E430277
|
entity |
| Predicate | leafAromaCompound |
P130024
|
FINISHED |
| Object | (E)-2-decenal |
—
|
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: (E)-2-decenal | Statement: [Coriandrum sativum, leafAromaCompound, (E)-2-decenal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leafAromaCompound Context triple: [Coriandrum sativum, leafAromaCompound, (E)-2-decenal]
-
A.
aromaticOilsPresent
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
B.
leafTaste
Indicates that one entity has a particular taste or flavor associated with its leaves.
-
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.
secondaryAroma
Indicates that an entity has a secondary or supporting aroma characteristic in addition to its primary scent.
-
E.
primaryAroma
Indicates the main or most dominant scent associated with an entity, distinguishing it from secondary or background aromas.
- F. None of above. chosen
Provenance (4 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29c6d0881909d450d2561d532a6 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.