Triple
T26123116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leotiomycetes |
E659028
|
entity |
| Predicate | typeOfAscomycete |
P153668
|
FINISHED |
| Object | Pezizomycotina ascomycete |
—
|
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: Pezizomycotina ascomycete | Statement: [Leotiomycetes, typeOfAscomycete, Pezizomycotina ascomycete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAscomycete Context triple: [Leotiomycetes, typeOfAscomycete, Pezizomycotina ascomycete]
-
A.
isAscomycetous
chosen
Indicates that an organism belongs to or exhibits characteristics of the Ascomycota (sac fungi) group.
-
B.
hymeniumType
Indicates the type or structure of the spore-bearing surface (hymenium) in a fungus, describing how and where its reproductive cells are arranged.
-
C.
hyphalType
Indicates the specific structural or morphological type of hyphae involved in a fungal relationship or process.
-
D.
hymenophoreType
Indicates the type or structure of the spore-bearing surface (hymenophore) an organism has, such as gills, pores, or ridges.
-
E.
fruitingBodyType
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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 26, 2026, 8:09 p.m.