Triple
T29179012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmonella spp. |
E739695
|
entity |
| Predicate | lactoseFermentation |
P166390
|
FINISHED |
| Object | non-lactose-fermenting |
—
|
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: non-lactose-fermenting | Statement: [Salmonella spp., lactoseFermentation, non-lactose-fermenting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lactoseFermentation Context triple: [Salmonella spp., lactoseFermentation, non-lactose-fermenting]
-
A.
fermentationBase
Indicates that one entity serves as the primary substrate or starting material used in the fermentation process that produces or transforms the other entity.
-
B.
lactoseContent
Indicates the amount or presence of lactose contained within a given substance or product.
-
C.
fermentationAgent
Indicates that one entity serves as the agent or catalyst that carries out the fermentation process on another entity.
-
D.
fermentationMethod
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
-
E.
isFermentedAs
Indicates that one substance undergoes a fermentation process to become another specified product.
- F. None of above. chosen
Provenance (4 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66343216c81909f1a6503d1538608 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:56 a.m.