Triple
T28694537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plasmopara |
E729376
|
entity |
| Predicate | diseaseManagement |
P165227
|
FINISHED |
| Object | fungicide application |
—
|
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: fungicide application | Statement: [Plasmopara, diseaseManagement, fungicide application]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diseaseManagement Context triple: [Plasmopara, diseaseManagement, fungicide application]
-
A.
diseaseContext
Indicates that the relationship or action occurs within, is influenced by, or is specifically relevant to a particular disease or pathological condition.
-
B.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
C.
diseaseUsed
Indicates that a particular disease is employed or utilized as a tool, model, or condition within a given context or process.
-
D.
basedOnDisease
Indicates that something (such as a decision, classification, or action) is determined or derived on the basis of a particular disease or disease-related information.
-
E.
diseaseName
Indicates that the associated value specifies the name or designation of a particular disease.
- F. None of above. chosen
Provenance (4 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:38 a.m.