Triple
T11466911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacillus |
E271801
|
entity |
| Predicate | sporeFunction |
P12475
|
FINISHED |
| Object | long-term survival |
—
|
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: long-term survival | Statement: [Bacillus, sporeFunction, long-term survival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sporeFunction Context triple: [Bacillus, sporeFunction, long-term survival]
-
A.
sporeType
Indicates the specific kind or category of spores associated with an entity.
-
B.
capsuleFunction
Indicates that a capsule is designed or used to perform a particular function, role, or therapeutic purpose.
-
C.
sporeFormation
chosen
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
-
D.
sporeResistance
Indicates the degree to which an entity can withstand or remain unaffected by spores or spore-related effects.
-
E.
PLEXFunction
Indicates a functional or operational role that one entity performs or serves for another within a system or context.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.