Triple
T23689815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venturiaceae |
E585264
|
entity |
| Predicate | responsibleForDisease |
P51727
|
FINISHED |
| Object | apple scab |
—
|
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: apple scab | Statement: [Venturiaceae, responsibleForDisease, apple scab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibleForDisease Context triple: [Venturiaceae, responsibleForDisease, apple scab]
-
A.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
B.
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.
-
C.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
D.
isPathogenOf
chosen
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
E.
diseaseVector
Indicates that one entity serves as a carrier or transmitter that spreads a disease-causing agent to another entity.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.