Triple
T23835440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valsaceae |
E590839
|
entity |
| Predicate | typicalDiseaseType |
P6645
|
FINISHED |
| Object | cankers |
—
|
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: cankers | Statement: [Valsaceae, typicalDiseaseType, cankers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDiseaseType Context triple: [Valsaceae, typicalDiseaseType, cankers]
-
A.
diseaseType
chosen
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
B.
diseaseContext
Indicates that the relationship or action occurs within, is influenced by, or is specifically relevant to a particular disease or pathological condition.
-
C.
includesDisease
Indicates that one entity (such as a category, group, or collection) contains or encompasses a particular disease as part of its members or elements.
-
D.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
E.
diseaseBurdenType
Indicates the type or category of burden (e.g., mortality, morbidity, economic impact) that a disease imposes.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f9eaa081909531f1322e0ec9ca |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:07 p.m.