Triple
T11466486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium |
E271793
|
entity |
| Predicate | cellWallProperty |
P99726
|
FINISHED |
| Object | lipid-rich cell wall |
—
|
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: lipid-rich cell wall | Statement: [Mycobacterium, cellWallProperty, lipid-rich cell wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellWallProperty Context triple: [Mycobacterium, cellWallProperty, lipid-rich cell wall]
-
A.
cellWallComponent
Indicates that one entity is a molecular or structural component of the cell wall of the other entity.
-
B.
cellWallContainsPeptidoglycan
Indicates that the cell wall of an organism includes peptidoglycan as one of its structural components.
-
C.
cellularComponent
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
D.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
-
E.
mechanicalProperty
Indicates a relationship where a mechanical characteristic (such as strength, stiffness, hardness, or elasticity) is attributed to or associated with an entity.
- 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_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. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.