Triple
T3019031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrtales |
E82407
|
entity |
| Predicate | containsEssentialOils |
P24581
|
FINISHED |
| Object | many species in Myrtaceae |
—
|
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: many species in Myrtaceae | Statement: [Myrtales, containsEssentialOils, many species in Myrtaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEssentialOils Context triple: [Myrtales, containsEssentialOils, many species in Myrtaceae]
-
A.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
B.
includesHerb
Indicates that one entity contains or incorporates a herb as part of its composition or contents.
-
C.
containsChemical
chosen
Indicates that one entity includes or has within it a specified chemical substance.
-
D.
traditionallyBelievedToContain
Indicates that something is customarily or historically thought to include or hold something else, regardless of whether this belief is factually accurate.
-
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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a927b608190ba1392498507b237 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.