Triple
T34208455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbellularia californica |
E877580
|
entity |
| Predicate | essentialOilCharacteristic |
P95361
|
FINISHED |
| Object | strongly aromatic |
—
|
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: strongly aromatic | Statement: [Umbellularia californica, essentialOilCharacteristic, strongly aromatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: essentialOilCharacteristic Context triple: [Umbellularia californica, essentialOilCharacteristic, strongly aromatic]
-
A.
seedEssentialOilComponent
Indicates that a component is an essential oil constituent derived specifically from a seed.
-
B.
aromaticOilsPresent
chosen
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
C.
characteristicAroma
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
D.
leafAromaCompound
Indicates that a particular aroma compound is present in, derived from, or characteristically associated with a plant’s leaves.
-
E.
commonScents
Indicates that two or more entities share the same or very similar smells or fragrances.
- 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_69f71052707c8190b6b514bf87a4bc79 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.