Triple
T26450284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taphrinomycotina |
E665328
|
entity |
| Predicate | hasTeleomorphType |
P67328
|
FINISHED |
| Object | ascomata often reduced or absent |
—
|
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: ascomata often reduced or absent | Statement: [Taphrinomycotina, hasTeleomorphType, ascomata often reduced or absent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeleomorphType Context triple: [Taphrinomycotina, hasTeleomorphType, ascomata often reduced or absent]
-
A.
hasTeleomorph
Indicates a relationship where one organism or taxon has a corresponding sexual (teleomorphic) form in its life cycle or classification.
-
B.
hyphalType
Indicates the specific structural or morphological type of hyphae involved in a fungal relationship or process.
-
C.
isAscomycetous
Indicates that an organism belongs to or exhibits characteristics of the Ascomycota (sac fungi) group.
-
D.
hymeniumType
Indicates the type or structure of the spore-bearing surface (hymenium) in a fungus, describing how and where its reproductive cells are arranged.
-
E.
fruitingBodyType
chosen
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 12:05 a.m.