Triple
T2238347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyathea |
E49334
|
entity |
| Predicate | reproductiveGeneration |
P5987
|
FINISHED |
| Object | dominant sporophyte generation |
—
|
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: dominant sporophyte generation | Statement: [Cyathea, reproductiveGeneration, dominant sporophyte generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproductiveGeneration Context triple: [Cyathea, reproductiveGeneration, dominant sporophyte generation]
-
A.
reproductionType
Indicates the mode or method by which an organism reproduces or generates offspring.
-
B.
reproductiveType
Indicates the mode or strategy by which an organism reproduces or generates offspring.
-
C.
reproductiveFeature
Indicates a relationship where an entity possesses or is characterized by a particular reproductive trait, structure, or capability.
-
D.
reproductionRate
Indicates the frequency or speed at which an entity produces new offspring or copies of itself over a given time or condition.
-
E.
dominantGeneration
chosen
Indicates that one generation in a life cycle is more prominent, long-lived, or visually conspicuous than the other generation(s).
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc096c7748190a545cc9b229bde62 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.