Triple
T22339469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boliniaceae |
E552234
|
entity |
| Predicate | hasFruitingBodyType |
P67328
|
FINISHED |
| Object | perithecial |
—
|
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: perithecial | Statement: [Boliniaceae, hasFruitingBodyType, perithecial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFruitingBodyType Context triple: [Boliniaceae, hasFruitingBodyType, perithecial]
-
A.
fruitingBodyType
chosen
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
-
B.
fruitingBodyColor
Indicates the color or coloration pattern of an organism’s fruiting body (the spore-producing structure).
-
C.
hasTeleomorph
Indicates a relationship where one organism or taxon has a corresponding sexual (teleomorphic) form in its life cycle or classification.
-
D.
fruitingBodyTexture
Indicates the type or quality of texture exhibited by an organism’s fruiting body in the context of its reproductive 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157824f588190882bea9e61dd5a83 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.