Triple
T5872353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microascales |
E130545
|
entity |
| Predicate | plantPathogensInclude |
P31424
|
FINISHED |
| Object | species causing root and stem diseases |
—
|
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: species causing root and stem diseases | Statement: [Microascales, plantPathogensInclude, species causing root and stem diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantPathogensInclude Context triple: [Microascales, plantPathogensInclude, species causing root and stem diseases]
-
A.
includesPathogensOf
chosen
Indicates that one entity contains or encompasses the pathogens that are associated with or originate from another entity.
-
B.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
C.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
D.
pathogenGenus
Indicates that one entity is a pathogen belonging to, or classified under, the specified genus.
-
E.
carriesPathogen
Indicates that one entity harbors and can transmit a disease-causing pathogen to another entity or environment.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.