Triple
T26158832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbiliomycetes |
E660046
|
entity |
| Predicate | fruitingBodyMorphology |
P147850
|
FINISHED |
| Object | small cup-like structures |
—
|
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: small cup-like structures | Statement: [Orbiliomycetes, fruitingBodyMorphology, small cup-like structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fruitingBodyMorphology Context triple: [Orbiliomycetes, fruitingBodyMorphology, small cup-like structures]
-
A.
fruitingBodyShape
chosen
Indicates the characteristic overall form or outline of an organism’s fruiting body in which spores are produced.
-
B.
fruitingBodyType
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
-
C.
fruitingBodyTexture
Indicates the type or quality of texture exhibited by an organism’s fruiting body in the context of its reproductive structure.
-
D.
fruitingBodyColor
Indicates the color or coloration pattern of an organism’s fruiting body (the spore-producing structure).
-
E.
hymeniumType
Indicates the type or structure of the spore-bearing surface (hymenium) in a fungus, describing how and where its reproductive cells are arranged.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c12d3708190ac08d8b7c8ff48a5 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:29 p.m.