Triple
T17544609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coriariaceae |
E427292
|
entity |
| Predicate | floralSex |
P8336
|
FINISHED |
| Object | unisexual or bisexual 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: unisexual or bisexual flowers | Statement: [Coriariaceae, floralSex, unisexual or bisexual flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floralSex Context triple: [Coriariaceae, floralSex, unisexual or bisexual flowers]
-
A.
flowerSex
chosen
Indicates that one entity has a specified sexual characteristic or reproductive role in relation to a flower.
-
B.
floweringUse
Indicates the use or application of something specifically for flowering or promoting the flowering process.
-
C.
flowerType
Indicates the specific kind or category of flower associated with an entity.
-
D.
flowerStructure
Indicates the structural characteristics or organization of a flower, such as the arrangement and form of its parts.
-
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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454609bdc8190b81b362906e7e3fd |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.