Triple
T29179040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmonella spp. |
E739695
|
entity |
| Predicate | antigenicStructure |
P78760
|
FINISHED |
| Object | O antigens |
—
|
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: O antigens | Statement: [Salmonella spp., antigenicStructure, O antigens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antigenicStructure Context triple: [Salmonella spp., antigenicStructure, O antigens]
-
A.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
-
B.
antigenicSubtype
Indicates a relationship where one entity is classified as a specific antigenic subtype or variant of another based on its antigenic properties.
-
C.
antigensExpressedOn
chosen
Indicates that specific antigens are present on the surface of a given cell or biological structure.
-
D.
antigenLocation
Indicates the location or site within an organism or environment where a specific antigen is present or found.
-
E.
solutionStructure
Indicates the structural or compositional arrangement that characterizes how a solution is organized or configured.
- 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_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. |
Created at: April 28, 2026, 11:56 a.m.