Triple
T28818174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteobacteria |
E727687
|
entity |
| Predicate | outerMembraneComponent |
P68689
|
FINISHED |
| Object | lipopolysaccharide |
—
|
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: lipopolysaccharide | Statement: [Proteobacteria, outerMembraneComponent, lipopolysaccharide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerMembraneComponent Context triple: [Proteobacteria, outerMembraneComponent, lipopolysaccharide]
-
A.
membraneType
Indicates the specific kind or classification of membrane associated with an entity.
-
B.
cellularComponent
chosen
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
C.
cellWallComponent
Indicates that one entity is a molecular or structural component of the cell wall of the other entity.
-
D.
cellWallContainsPeptidoglycan
Indicates that the cell wall of an organism includes peptidoglycan as one of its structural components.
-
E.
membraneLipidType
Indicates the specific type or class of lipid that composes or is associated with a membrane.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f54d4c819098307e82a2a6e892 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:33 a.m.