Triple
T37945775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terribacillus |
E946601
|
entity |
| Predicate | endosporeFormation |
P12475
|
FINISHED |
| Object | subterminal 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: subterminal endospores | Statement: [Terribacillus, endosporeFormation, subterminal endospores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endosporeFormation Context triple: [Terribacillus, endosporeFormation, subterminal endospores]
-
A.
sporeFormation
chosen
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
-
B.
ascosporeFeature
Indicates a specific characteristic, quality, or attribute associated with an ascospore in the described relationship or context.
-
C.
biofilmFormation
Indicates the process or capability of forming a biofilm, where microorganisms adhere to a surface and to each other within a protective matrix.
-
D.
fruitingBodyType
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
-
E.
fruitingBodyShape
Indicates the characteristic overall form or outline of an organism’s fruiting body in which spores are produced.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.