Triple
T23030505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botrytis cinerea |
E573441
|
entity |
| Predicate | diseaseSymptom |
P2896
|
FINISHED |
| Object | gray moldy growth |
—
|
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: gray moldy growth | Statement: [Botrytis cinerea, diseaseSymptom, gray moldy growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diseaseSymptom Context triple: [Botrytis cinerea, diseaseSymptom, gray moldy growth]
-
A.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
-
B.
symptom
chosen
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
C.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
D.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
E.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18481072c81909ab2a2c87e034433 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.