Triple
T14426927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yersinia |
E357719
|
entity |
| Predicate | biosafetyLevelOfSomeSpecies |
P63409
|
FINISHED |
| Object | BSL-3 |
—
|
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: BSL-3 | Statement: [Yersinia, biosafetyLevelOfSomeSpecies, BSL-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biosafetyLevelOfSomeSpecies Context triple: [Yersinia, biosafetyLevelOfSomeSpecies, BSL-3]
-
A.
hasBiosafetyLevel
chosen
Indicates that an entity (such as a facility, lab, or area) is assigned a specific biosafety level that defines the containment and safety measures required for handling biological agents there.
-
B.
biosafetyConcernMember
Indicates that an entity is a member, participant, or component of a biosafety-related concern or issue.
-
C.
zoonoticPotential
Indicates the potential for a disease or pathogen to be transmitted from animals to humans.
-
D.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
-
E.
pathogenicityToHumans
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.