Triple
T23835856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diaporthe citri |
E590850
|
entity |
| Predicate | firstDescribedAsPathogenOf |
P82256
|
FINISHED |
| Object | citrus |
—
|
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: citrus | Statement: [Diaporthe citri, firstDescribedAsPathogenOf, citrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDescribedAsPathogenOf Context triple: [Diaporthe citri, firstDescribedAsPathogenOf, citrus]
-
A.
discoveredAsPathogen
chosen
Indicates that an entity was identified or recognized as a disease-causing pathogen.
-
B.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
C.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
D.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
-
E.
firstDescribedAs
Indicates the original way or terms in which something was initially characterized, named, or documented.
- 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.