Triple
T37449453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aliivibrio |
E930637
|
entity |
| Predicate | associatedWithDiseaseIn |
P76100
|
FINISHED |
| Object | salmonids |
—
|
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: salmonids | Statement: [Aliivibrio, associatedWithDiseaseIn, salmonids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDiseaseIn Context triple: [Aliivibrio, associatedWithDiseaseIn, salmonids]
-
A.
hasAssociatedDisease
chosen
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
B.
associatedDiseaseAgentType
Indicates the type or category of disease-causing agent that is associated with a given disease or condition.
-
C.
hasEponymousDisease
Indicates that an entity (typically a person) has a disease named after them.
-
D.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
E.
associatedWithPhenotype
Indicates that an entity has a documented connection or correlation with a particular phenotype or observable trait.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.