Triple
T35945652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feijoa sellowiana |
E1039579
|
entity |
| Predicate | selfFertility |
P55490
|
FINISHED |
| Object | often self-incompatible |
—
|
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: often self-incompatible | Statement: [Feijoa sellowiana, selfFertility, often self-incompatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfFertility Context triple: [Feijoa sellowiana, selfFertility, often self-incompatible]
-
A.
fertility
Indicates the capacity or potential of an entity to reproduce or generate offspring.
-
B.
fertilityStatus
chosen
Indicates the reproductive condition or capability of an entity, such as whether it is fertile, infertile, or at a particular stage of fertility.
-
C.
hasFertility
Indicates that one entity possesses or exhibits the capacity to reproduce or generate offspring.
-
D.
reproductiveCare
Indicates the provision or receipt of services, support, or actions related to an entity’s reproductive health and reproductive processes.
-
E.
fertilizationType
Indicates the method or process by which fertilization occurs or is achieved between reproductive cells.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.