Triple
T23147008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronidium |
E578220
|
entity |
| Predicate | hasFoliageScent |
P23045
|
FINISHED |
| Object | citrus-like aroma |
—
|
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: citrus-like aroma | Statement: [Coronidium, hasFoliageScent, citrus-like aroma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoliageScent Context triple: [Coronidium, hasFoliageScent, citrus-like aroma]
-
A.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
B.
foliageCharacteristic
Indicates the specific traits or qualities of an entity’s foliage, such as its type, texture, color, or other distinguishing features.
-
C.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
-
D.
hasFragrance
chosen
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
E.
hasForagingAbility
Indicates that an entity possesses the capability or skill to search for and obtain food or resources.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecee3808190aadc65c312f79f32 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.