Triple
T8961458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smuts |
E214014
|
entity |
| Predicate | hostTissueEffect |
P19730
|
FINISHED |
| Object | replacement of host tissues by fungal spores |
—
|
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: replacement of host tissues by fungal spores | Statement: [Smuts, hostTissueEffect, replacement of host tissues by fungal spores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTissueEffect Context triple: [Smuts, hostTissueEffect, replacement of host tissues by fungal spores]
-
A.
infectsTissue
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
-
B.
hasTissue
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
-
C.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
-
D.
immuneEvasionMechanism
Indicates a mechanism by which an entity avoids, suppresses, or otherwise interferes with detection or elimination by an immune system.
-
E.
healthEffect
chosen
Indicates the impact or consequence that one entity has on the health or well-being of another.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6748baa88190ac54e701dc4d6212 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.