Triple
T3873380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elaeagnus |
E92438
|
entity |
| Predicate | flowerScent |
P12303
|
FINISHED |
| Object | often fragrant flowers |
—
|
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: often fragrant flowers | Statement: [Elaeagnus, flowerScent, often fragrant flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowerScent Context triple: [Elaeagnus, flowerScent, often fragrant flowers]
-
A.
flowerType
Indicates the specific kind or category of flower associated with an entity.
-
B.
floweringUse
Indicates the use or application of something specifically for flowering or promoting the flowering process.
-
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.
flowerCharacteristic
chosen
Indicates that a flower possesses a particular attribute, quality, or feature (such as color, shape, size, or scent).
-
E.
flowerStructure
Indicates the structural characteristics or organization of a flower, such as the arrangement and form of its parts.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.