Triple
T34349810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nectandra |
E881534
|
entity |
| Predicate | hasAromaticCompounds |
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: [Nectandra, hasAromaticCompounds, essential oils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAromaticCompounds Context triple: [Nectandra, hasAromaticCompounds, essential oils]
-
A.
aromaticOilsPresent
chosen
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
B.
isAromaticVariety
Indicates that one entity is a variety or type of another that is specifically characterized by having a notable or distinctive aroma.
-
C.
hasAromaticPart
Indicates that one entity includes or contains a structural component that is aromatic.
-
D.
isAromatic
Indicates that an entity possesses aromatic character, typically involving a conjugated ring system with delocalized electrons that confer special stability or scent-related properties.
-
E.
lessAromaticThan
Indicates that one entity has a lower degree of aromaticity than another 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:58 a.m.