Triple
T34208428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbellularia californica |
E877580
|
entity |
| Predicate | aromaSimilarTo |
P155222
|
FINISHED |
| Object | bay laurel (Laurus nobilis) |
—
|
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: bay laurel (Laurus nobilis) | Statement: [Umbellularia californica, aromaSimilarTo, bay laurel (Laurus nobilis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aromaSimilarTo Context triple: [Umbellularia californica, aromaSimilarTo, bay laurel (Laurus nobilis)]
-
A.
commonScents
chosen
Indicates that two or more entities share the same or very similar smells or fragrances.
-
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.
aromaticOilsPresent
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:55 a.m.