Triple
T1125839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiostoma novo-ulmi |
E24717
|
entity |
| Predicate | virulence |
P25252
|
FINISHED |
| Object | highly virulent |
—
|
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: highly virulent | Statement: [Ophiostoma novo-ulmi, virulence, highly virulent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virulence Context triple: [Ophiostoma novo-ulmi, virulence, highly virulent]
-
A.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
-
B.
pathogenicityToHumans
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
-
C.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
D.
infectsTissue
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
-
E.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.