Triple
T23557134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paramignya |
E578214
|
entity |
| Predicate | flowerTrait |
P12303
|
FINISHED |
| Object | small white or pale 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: small white or pale flowers | Statement: [Paramignya, flowerTrait, small white or pale flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowerTrait Context triple: [Paramignya, flowerTrait, small white or pale flowers]
-
A.
flowerCharacteristic
chosen
Indicates that a flower possesses a particular attribute, quality, or feature (such as color, shape, size, or scent).
-
B.
agronomicTrait
Indicates a relationship where a trait is characterized specifically in terms of its relevance to agricultural growth, management, or productivity of plants or crops.
-
C.
flowerType
Indicates the specific kind or category of flower associated with an entity.
-
D.
flowerFunction
Indicates the biological or practical role that a flower serves, such as reproduction, attraction of pollinators, or ornamental use.
-
E.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af659e9881908b527accfd2b1187 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.