Triple
T37450607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pectobacterium |
E930660
|
entity |
| Predicate | diseaseMechanism |
P68675
|
FINISHED |
| Object | degradation of plant cell walls |
—
|
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: degradation of plant cell walls | Statement: [Pectobacterium, diseaseMechanism, degradation of plant cell walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diseaseMechanism Context triple: [Pectobacterium, diseaseMechanism, degradation of plant cell walls]
-
A.
pathogenicMechanism
chosen
Indicates the specific biological process or mechanism through which an agent causes disease or pathological effects in a host.
-
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.
humanDisease
Indicates that the subject is a disease that affects humans.
-
D.
targetsPathophysiology
Indicates that an intervention, agent, or process is specifically directed at modifying or influencing a particular disease mechanism or pathological process.
-
E.
causesDiseaseType
Indicates that one entity is responsible for causing a specific type or category of disease in another entity.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.