Triple
T19808851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leucadendron |
E475886
|
entity |
| Predicate | hasSexesOnSeparatePlants |
P137397
|
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: [Leucadendron, hasSexesOnSeparatePlants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSexesOnSeparatePlants Context triple: [Leucadendron, hasSexesOnSeparatePlants, true]
-
A.
flowerSex
Indicates that one entity has a specified sexual characteristic or reproductive role in relation to a flower.
-
B.
hasSexualReproduction
Indicates that an entity reproduces through sexual reproduction, involving the combination of genetic material from two (or more) parents.
-
C.
isSelfPollinating
Indicates that an organism or plant can fertilize itself without requiring pollen from another individual.
-
D.
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.
-
E.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65429fec8819091e20908101b50eb |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.