Triple
T37379466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clostridiales |
E928390
|
entity |
| Predicate | sporesResistance |
P40202
|
FINISHED |
| Object | heat-resistant endospores |
—
|
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: heat-resistant endospores | Statement: [Clostridiales, sporesResistance, heat-resistant endospores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sporesResistance Context triple: [Clostridiales, sporesResistance, heat-resistant endospores]
-
A.
sporeResistance
chosen
Indicates the degree to which an entity can withstand or remain unaffected by spores or spore-related effects.
-
B.
isResistant
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
C.
pestResistance
Indicates that an entity has the ability to withstand, deter, or remain unaffected by damage or harm caused by pests.
-
D.
confersResistanceTo
Indicates that one entity provides or imparts resistance or reduced susceptibility to another entity against a specified agent, condition, or effect.
-
E.
isBacteriaResistant
Indicates that a bacterium is not inhibited or killed by a particular antibiotic or antimicrobial treatment.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.