Triple
T5691014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malvales |
E125426
|
entity |
| Predicate | typicalStamens |
P65977
|
FINISHED |
| Object | numerous stamens often fused into a tube |
—
|
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: numerous stamens often fused into a tube | Statement: [Malvales, typicalStamens, numerous stamens often fused into a tube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStamens Context triple: [Malvales, typicalStamens, numerous stamens often fused into a tube]
-
A.
stamenCount
Indicates the number of stamens present in a flower or floral structure.
-
B.
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.
-
C.
petalCount
Indicates the number of petals associated with an entity, typically a flower or floral structure.
-
D.
inflorescenceType
Indicates the specific kind or arrangement of a plant’s flower cluster in which its flowers are borne.
-
E.
typicalSeed
Indicates that something is a usual or characteristic seed for a given plant or context.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:44 p.m.