Triple
T425210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryophyta |
E8191
|
entity |
| Predicate | sporangiumPosition |
P14753
|
FINISHED |
| Object | terminal on sporophyte |
—
|
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: terminal on sporophyte | Statement: [Bryophyta, sporangiumPosition, terminal on sporophyte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sporangiumPosition Context triple: [Bryophyta, sporangiumPosition, terminal on sporophyte]
-
A.
gametophyteType
Indicates the specific kind or form of gametophyte (the haploid, gamete-producing life stage) associated with an organism or taxon.
-
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.
leafArrangement
Indicates how leaves are positioned or organized on a plant’s stem or branches.
-
D.
sporeType
Indicates the specific kind or category of spores associated with an entity.
-
E.
sporeFormation
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.