Triple
T23835464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valsaceae |
E590839
|
entity |
| Predicate | asexualMorphOftenPlacedIn |
P153790
|
FINISHED |
| Object | Cytospora |
—
|
NE NERFINISHED |
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: Cytospora | Statement: [Valsaceae, asexualMorphOftenPlacedIn, Cytospora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asexualMorphOftenPlacedIn Context triple: [Valsaceae, asexualMorphOftenPlacedIn, Cytospora]
-
A.
hasAsexualMorph
Indicates that an entity possesses or is associated with an asexual morphological form in its life cycle.
-
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.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
-
D.
ovulePosition
Indicates the spatial placement or arrangement of ovules within or on the ovary or related reproductive structure.
-
E.
sporangiumPosition
Indicates the relative location or arrangement of a sporangium in or on the structure that bears it.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f9eaa081909531f1322e0ec9ca |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:07 p.m.