Triple
T36827388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirogyra |
E910046
|
entity |
| Predicate | asexualReproductionMethod |
P184716
|
FINISHED |
| Object | fragmentation |
—
|
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: fragmentation | Statement: [Spirogyra, asexualReproductionMethod, fragmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asexualReproductionMethod Context triple: [Spirogyra, asexualReproductionMethod, fragmentation]
-
A.
asexualReproductionMode
chosen
Indicates the method or process by which an organism reproduces asexually, without the fusion of gametes.
-
B.
reproductionType
Indicates the mode or method by which an organism reproduces or generates offspring.
-
C.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
-
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.
hasTypeOfReproductionStructure
Indicates that one entity possesses or exhibits a particular kind of reproductive structure associated with its mode of reproduction.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.