Triple
T38560776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterococcus |
E928070
|
entity |
| Predicate | bileTolerance |
P582
|
FINISHED |
| Object | able to grow in presence of bile salts |
—
|
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: able to grow in presence of bile salts | Statement: [Enterococcus, bileTolerance, able to grow in presence of bile salts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bileTolerance Context triple: [Enterococcus, bileTolerance, able to grow in presence of bile salts]
-
A.
tolerates
chosen
Indicates that one entity endures, accepts, or allows the presence, behavior, or condition of another entity without intervening to stop or change it.
-
B.
intolerantOf
Indicates that one entity has a negative, adverse, or non-accepting reaction to another entity, such that it cannot tolerate its presence, properties, or effects.
-
C.
saltTolerance
Indicates the degree to which an entity can withstand or function under saline (high-salt) conditions.
-
D.
hasBitternessLevel
Indicates that an entity is associated with a specific degree or intensity of bitterness.
-
E.
bitterantType
Indicates the specific kind or category of bitterant used or associated with an 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.