Triple
T35948617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stylapterus |
E1039655
|
entity |
| Predicate | hasSpecializedFloralStructures |
P197716
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stylapterus, hasSpecializedFloralStructures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecializedFloralStructures Context triple: [Stylapterus, hasSpecializedFloralStructures, true]
-
A.
hasSpecializedPetal
Indicates that an entity possesses petals that are specialized or modified for a particular function or role.
-
B.
hasFloralWhorlCount
Indicates the number of floral whorls present in a flower.
-
C.
reproductiveStructure
Indicates that one entity serves as a reproductive organ or structure of another, involved in producing or facilitating the formation of offspring or reproductive cells.
-
D.
flowerStructure
Indicates the structural characteristics or organization of a flower, such as the arrangement and form of its parts.
-
E.
hasAndroecium
Indicates that an organism or flower possesses an androecium, i.e., the male reproductive structure(s) of a flower.
- F. None of above. chosen
Provenance (4 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:07 p.m.