Triple
T393440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiostoma |
E8929
|
entity |
| Predicate | hasSpecies |
P965
|
FINISHED |
| Object | Ophiostoma ulmi |
E3941
|
NE 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: Ophiostoma ulmi | Statement: [Ophiostoma, hasSpecies, Ophiostoma ulmi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ophiostoma ulmi Context triple: [Ophiostoma, hasSpecies, Ophiostoma ulmi]
-
A.
Ophiostoma ulmi
chosen
Ophiostoma ulmi is a pathogenic fungus best known for causing the devastating tree epidemic known as Dutch elm disease.
-
B.
Ophiostoma novo-ulmi
Ophiostoma novo-ulmi is a highly virulent fungal pathogen responsible for the most destructive modern pandemic of Dutch elm disease in elm trees worldwide.
-
C.
Ophiostoma
Ophiostoma is a genus of fungi best known for containing species that cause Dutch elm disease in elm trees.
-
D.
Ophiostomataceae
Ophiostomataceae is a family of fungi that includes several important tree pathogens, notably species responsible for Dutch elm disease.
-
E.
Dutch elm disease
Dutch elm disease is a devastating fungal infection spread by elm bark beetles that has killed millions of elm trees worldwide, particularly in Europe and North America.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec7637c08190b695ec640edbf6c2 |
completed | Feb. 28, 2026, 1:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a413f1148481908b4a25355ee07069 |
completed | March 1, 2026, 10:24 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.