Triple
T6494064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meliolales |
E148110
|
entity |
| Predicate | characteristicSymptom |
P2896
|
FINISHED |
| Object | black sooty growth on leaf surfaces |
—
|
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: black sooty growth on leaf surfaces | Statement: [Meliolales, characteristicSymptom, black sooty growth on leaf surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicSymptom Context triple: [Meliolales, characteristicSymptom, black sooty growth on leaf surfaces]
-
A.
symptom
chosen
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
C.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
D.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
E.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab7c0b8819091437a293b40dfd2 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.