Triple
T37591217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudomonadales |
E935264
|
entity |
| Predicate | notablePathogenicSpecies |
P99744
|
FINISHED |
| Object | Pseudomonas aeruginosa |
E930646
|
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: Pseudomonas aeruginosa | Statement: [Pseudomonadales, notablePathogenicSpecies, Pseudomonas aeruginosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePathogenicSpecies Context triple: [Pseudomonadales, notablePathogenicSpecies, Pseudomonas aeruginosa]
-
A.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
B.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
C.
pathogenGenus
Indicates that one entity is a pathogen belonging to, or classified under, the specified genus.
-
D.
pathogenicityToHumans
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
-
E.
pathogenicMember
chosen
Indicates that an entity is a member of a group or set that is characterized as pathogenic (capable of causing disease).
- F. None of above.
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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f167bd688190b00138d14cd3ad17 |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.